The Custom Data Fields feature allows you to define your own columns to show in the Shipment Explorer, mapping nearly any data field from CargoWise One that your customers may need to see. For more information on the feature, see Bring Custom Data Fields into Logixboard.
Steps
1. Email [email protected] with the column name(s) for each data field to be displayed in the Shipments Explorer.
Data Field in CW1 | Column Name in LXB |
Weight | Weight |
Weight unit | Weight Unit |
Vol | Volume |
Vol unit | Volume Unit |
Chargeable | Chargeable |
Incoterm | Incoterm |
💡Note: If a data point has a secondary related field (e.g., unit), that will require an additional column.
2. Include whether the field is part of a collection; if it is, the Logixboard team will need to assess the request on a per-case basis, as some cannot be pulled from the CW1 XML. We will work with you on assessing and providing options.
Here’s an example of a data field that is part of a collection:
3. Is this field relevant for Forwarding Shipments, Brokerage files, or both?
4. Include a screenshot from CW1 showing the value to be mapped. This will help ensure the correct fields are mapped in.
5. (Optional) Screenshots with highlighted data field from the XML
If possible, please provide the specific data element within the CW1 XML. This is an optional step, but helps ensure the correct fields are mapped.
How to find the Shipment XML in CargoWise
Locate the specific shipment you're interested in in CW1
Go to Workflow & Tracking > Events
Filter by Event Code starts with DEX and Reference contains LXB
Select and go through the search results
Look for Data Type: XUS - XML Universal Shipment and click View
Download the XML by clicking on Save to Disk
Use Ctrl + F to find your required data field in the downloaded XML file.
If you cannot find the data field, we will not be able to support the data field. Please use the custom data field in CargoWise to customize any desired data field.
Important Notes - General
Custom fields are supported for Forwarding Shipments and B-Files only.
Simple data fields are best suited for this feature (e.g., identifiers, short text strings, simple properties).
Complex multi-part data fields may be possible but need to be assessed case-by-case.
Company-specific fields are not currently supported.
Fields that are part of an array of nested collections may not be possible to extract and will be assessed case-by-case.
Lists (e.g., comma-separated Container Numbers) are not currently supported.
For any issues or questions, please reach out to the support team.