Existing customer? log in now
You can use the "Field assignments" menu item to create an individual assignment between the fields defined in your customer's protocol and the fields available in our system.
On the left-hand side of the mapping tool, select the target field of the desired protocol (e.g. OCI), then select the desired mapping type (database, fixed value, dynamic (only for gateway mode).
On the right-hand side, select the source field and/or the value to be assigned to the respective protocol field.
Database: In the "Source field" field, select a field from our data model that is to be used as the data source for the selected target field during transmission.
Fixed value: In the "Source field" field, enter a fixed value that is to be output in the selected target field during transmission to the calling ERP system.
Dynamic: This assignment type is only available for the Gateway mode. Here it is possible to transfer and assign further data in the "product" object during the retransfer from the called shop system.
...
"additionalProp1": [
{
"label": "string",
"value": "string"
},
{
"label": "string",
"value": "string"
}
],
...
Example: In the "product" object, you also transfer the "classifications" array, which in turn contains objects with the keys label and value. Here you have the option of storing the key description classifications in the first input field and the value of the key label in the second. The value field of the same object is now used for the field assignment.
Field transformations allow you to dynamically change values in your field mappings before they are transferred to the target system. You can use transformations to convert input values into other values based on defined rules.
To create or edit a transformation for a field:
The transformation type "Replace value " (If transformation) is currently supported. This transformation checks whether the input value matches a defined value and replaces it with another value if necessary.
Use payload as fallback: If activated, the original value is adopted unchanged if no match is found.
If your source system uses status values such as "0" and "1", but the target system expects "Inactive" and "Active":
If your source system uses language codes in "de-DE" format, but the target system only expects "de":
If you want to ensure that empty values are replaced by a default value: