When you configure rule associations for data enrichment in Business 360 Console, consider the following guidelines to map input and output fields:
•When you map input fields, map all required fields from data providers.
•When you map output fields, map all required business entity fields or relationships in a hierarchy model.
•To enrich the existing entries of a field group, ensure that you map the field group as one of the input fields. For example, if you want to enrich the existing Phone field group entries, you must map the Phone field group as an input field.
•When you map input fields, map the compatible business entity fields to the data provider fields.
The following table lists the compatible data types of business entity fields:
Data types of business entity fields
Data types of data provider fields
Sample Values
Boolean
Boolean, Text
true, false, "true", "false"
Integer
Integer, Double, Decimal, Text
123, "123"
Double
Double, Text
123.45, "123.45"
Decimal
Decimal, Text
123.45, "123.45"
Date
Date, Text
"2025-10-15"
Date and time
Date and time, Text
"1672531200000"
Text
Text
"John Doe"
Picklist
Text
"US"
•When you map output fields, map the compatible data provider fields to the business entity fields.
The following table lists the compatible data types of data provider fields:
Data types of data provider fields
Data types of business entity fields
Sample values
Boolean
Boolean, Text
true, false, "true", "false"
Integer
Integer, Double, Decimal, Text
123, "123"
Decimal
Decimal, Text
123.45, "123.45"
Double
Double, Text
123.45, "123.45"
Date
Date, Text
"2025-10-15"
Date and time
Date and time, Text
"1672531200000"
Text
Text, Picklist, Boolean, Integer, Double, Decimal, Date, Date and Time
•If you map a text field from a data provider to a non-text field in a business entity, ensure that the text field contains valid data. For example, you map the text field Amount to the decimal field Amount in a business entity. Ensure that the text field from the data provider contains valid data, such as "500.00", and not invalid data, such as "five hundred."
•If you map a text field to a picklist in a business entity, ensure that the text field contains a valid picklist code value.
•When you map input fields in a rule association, don't map system fields. If you map system fields, the rule association isn't triggered when records are created or updated.
Mapping field groups for data enrichment
When you map field groups in a rule association for data enrichment, consider the following restrictions:
•You can’t map multiple field groups to the same target field group. For example, you can't map the field groups named Email and Phone from a business entity to the Contacts field group of the data provider.
The following image shows an invalid field group mapping with multiple field groups mapped to a target field group:
•You can’t map multiple field groups to root fields. For example, you can't map the field groups named Email and Phone from a business entity to the Email and Phone root fields of the data provider. You can map only one field group to the fields at the same level.
The following image shows an invalid field group mapping with multiple field groups mapped to target root fields:
•When you map nested field groups, you can’t map multiple sibling field groups to a target field group.
The following image shows an invalid nested field group mapping:
•If a business entity field group isn't mapped in the input mapping and you map the field group in the output mapping, ensure that you map all required fields in the field group. If you don’t map all required fields in the field group, you can’t save the rule association. For example, if the business entity Address field group isn't mapped in the input mapping and you map a field group to the Address field group in the output mapping, map all required fields in the Address field group.
