cXML – Configure Fields
In the Fields tab, which product data is transferred per line item in the PunchOutOrderMessage is defined.
How do fields work?
The field configuration works identically to OCI: a primary data field and up to three fallbacks are defined for each XML data point. The connector uses the first value that is not empty.
XML field Primary field Fallback 1 Fixed value
Description → productName or productNumber or "Product"
Adding Fields
| Property | Description |
|---|---|
| Name | XML field identifier as it should appear in the PunchOutOrderMessage |
| Data field | Primary data source from the library |
| Fallback 1–3 | Used when the previous field returns no value |
| Fixed value | Static text as last fallback |
| Position | Sort order |
Available Data Fields
A complete overview of all data fields — including which protocols (OCI, cXML) they are available for — can be found here:
Filters
Every field can pass its resolved value through a filter before output. Filters are enabled in the field dialog.
| Filter | Settings | Effect |
|---|---|---|
| Substring | Start, End | Outputs only the section of the text between start and end |
| Display decimals | Decimals | Formats the value as a decimal number with a fixed number of decimal places |
| Divide by | Value | Divides the numeric value by the given divisor |
| System price digits | – | Formats the value with the decimals configured for this system in the General tab |
Filters configured for cXML fields had no effect in earlier versions. From this version on they change the generated XML. The field configuration of existing cXML systems should therefore be reviewed before productive integrations are updated.
System price digits and Display decimals are mutually exclusive — only one of them can be active at a time. Substring should not be combined with the numeric filters.
Shipping & Tax
The <Shipping> and <Tax> header blocks are not configured in this tab but in their own Shipping and Tax tabs via field trees — see Shipping & Tax.