3. Field Mapping Component

Fixed Value

Solution scenario: The target object has this field but the source object has no corresponding field. To ensure target data completeness (for example, when the field is required), you can set a fixed value to write into the target.

For example:

Entry point: In the source field dropdown, select “Fixed Value Mapping”

For non-enum types, enter the fixed value directly. For enum (picklist) types, choose one fixed value from the target field’s option list.

Default Value

Solution scenario: When the source field value is empty (how the system defines “empty” can be configured — see below), to ensure target data completeness (for example, when the field is required), you can specify a default value.

For example: If the order amount is empty, synchronize a default value of 0.

Entry point:

First select the source field; hover over the field box to reveal the “Set Default Value” action.

Using “Default Value” to Handle Empty Value Conversion / Define Empty Meaning

// Configuration method updated on Nov 23

1. When the source field value is empty, you can configure how to convert that empty value. Options include empty string, NULL, empty collection, or 0.

1. You can configure what “source field is empty” means.

The meanings of the following configurations:

When the source field is NULL, or the external system does not have this field, convert the source field value to an empty string.

1. “Field does not exist”: the external object simply does not have this field.
2. “Source field is null/field does not exist”: when you do not modify the configuration, this is the default. NULL denotes a null value; empty string/whitespace are not NULL.

Quick Option Mapping

For enum (picklist) fields, when the source and target have many option values that largely match, use “Auto-map by sub-option name” to map them in one click rather than mapping each one manually.

For example: product series, Unit, etc. Entry point:

Quick Field Mapping

When the source and target objects require many field mappings and the names and types largely match, use “Map by Name and Type” to map all at once instead of mapping individually.

Entry point:

Additionally, some K3C objects provide template-based mapping; templates include commonly used field mappings.

Set Fields to Not Update

Scenario: Some fields should only be set on create and should not be updated. You can mark those fields as “Do Not Update.”

Entry point: Integration Flow -> Field Mapping -> top-right “Settings”

Set any target system fields that have mapping configured to “Do Not Update” if they should not be updated.

Lookup / Multi-Select Lookup Validation

Scenario:

For lookup-type fields in business data, the platform looks up associated data in the target object’s mapping table based on the source field value to establish the association. If no match is found, the platform reports an error.

However, sometimes the integration does not require linking to the associated object’s data. In that case, set the field’s validation to “No Validation” so the system will not throw an error if it does not find the associated record.

Entry point: Field Mapping Component -> Settings

You can configure this for Lookup and Multi-Select Lookup fields. The default is validation enabled; you can change it to no validation.

Validation logic: If the source field has a value but no mapped data is found, the system throws an error and the sync status is marked as Failed.

No-validation logic: If the source field has a value but no mapped data is found, the system does not throw an error and the sync status is marked as Success.