Input Header mapping
Users can now align their source system headers (e.g. Shipment_ID instead of Consgnment_ID) with our internal system names without altering their original files. This eliminates the need for manual transformations of column names.
How To Use:
- Navigate to the Definitions page.
- Locate the editable Input Column columns.
- Edit the desired field name (e.g. change "Customer Name" to "Client").
- Upload a file that uses your own headers.
Behavior Rules:
- One-to-One Mapping Enforcement:
If both the original header (customer_name) and a renamed version (Client_Name) exist in a single upload, the system will reject the file.
→ Only one mapped name should be present in the input file. - Recognition during Upload:
- Mapped headers will be recognized just like original headers during data ingestion.
- Original headers are also still recognized
- You can only edit Input Column values that exist in input files. Rows with category Output or Measure are not alterable.
- Process API: No changes applied. API responses and requests retain original naming conventions from before.
→ ⚠️ This is intentional to avoid breaking changes but should be noted for API consumers.