3. Field Mapping Component

Fixed Value

Use case: When the target object has a field but the source object lacks a corresponding field, you can set a fixed value to ensure data integrity in the target object (e.g., for required fields).

Example:

picture coming soon:

Configuration: Select “Fixed Value Mapping” from the source field dropdown menu.

picture coming soon:

• For non-enumeration fields: Enter the fixed value directly.
• For enumeration fields: Select a fixed value from the target field’s options.

picture coming soon:

Default Value

Use case: When a source field is empty (configurable definition of “empty”), you can specify a default value to maintain target data integrity (e.g., for required fields).

Example: When an order amount is empty, synchronize a default value of 0.

picture coming soon:

Configuration: 1. Select the source field 2. Hover over the field to display the “Set Default Value” option

picture coming soon:

Handling Empty Values via Default Values (Format Conversion/Empty Definition Configuration)

//Updated configuration method as of November 23

1. Configure how to handle empty source field values by selecting from: empty string, NULL, empty collection, or 0.

picture coming soon:

1. Configure the meaning of “empty” for source fields:

The following configuration means: When the source field value is NULL or the field doesn’t exist in the external system, convert the source field value to an empty string.

picture coming soon:

picture coming soon:

Notes: 1. “Field doesn’t exist”: The external object completely lacks this field 2. “Source field value is NULL/Field doesn’t exist”: Default configuration if not modified. NULL means empty, while empty strings/whitespace don’t count as NULL.

Quick Mapping for Option Values

For enumeration fields with numerous options that are largely consistent between source and target fields, use “Auto-map by Option Name” for one-click mapping instead of manual pairing.

Example: Product series or Unit fields for materials.

Configuration:

picture coming soon:

Quick Field Mapping

When numerous fields need mapping between source and target objects with similar names and types, use “Map by Name and Type” for one-click mapping instead of manual pairing.

Configuration:

picture coming soon:

Note: For K3C objects, template-based mapping is also available, featuring commonly used pre-mapped fields.

Configure No-Value Updates

Use case: For fields that should only be populated during creation (not updated), set them to “No Update”.

Configuration: Integration Flow > Field Mapping > Settings (top-right)

picture coming soon:

Set target system fields with field mappings to “No Update” as needed.

picture coming soon:

Lookup Association Validation (Single/Multi-select)

Use case: For lookup association fields, the platform searches the associated object’s intermediate table using the source field value. If no match is found, the system reports an error.

However, some business scenarios don’t require associated object data. Set these fields to “No Validation” to prevent errors when associated data isn’t found.

Configuration: Field Mapping Component > Settings

Available for lookup association and multi-select lookup association fields. Default is “Validate”, which can be changed to “No Validate”.

Validation logic: - When enabled: System reports errors and marks sync status as “Exception” if source field has value but no mapping data is found - When disabled: System doesn’t report errors and marks sync status as “Success” if source field has value but no mapping data is found

picture coming soon: