After you upload the source file, select the appropriate target business entities, relationships, or hierarchies to which you want to import data.
Based on the target business entities, relationships, or hierarchies that you select, the import process automatically maps the columns of your source file to suitable target fields. For each mapped field, a confidence indicator appears that indicates the level of confidence of the field mapping.
If you are not in agreement with the system-suggested field mapping, manually map the source columns with the appropriate target fields. If you use any field in a field group, ensure that you map all the required fields of the field group.
The following table describes the confidence indicators:
Confidence Indicator
Description
Indicates a high level of confidence with the field mapping.
Indicates a medium level of confidence with the field mapping. If you are not in agreement with this mapping, delete this mapping and modify the field mapping as required.
Indicates a low level of confidence with the field mapping. If you are not in agreement with this mapping, delete this mapping and modify the field mapping as required.
The following image shows some mapped fields with confidence indicators:
You can map the Source Last Updated Date of root fields and field groups. The Source Last Updated Date field captures the last updated date of fields in the source records. By default, when you import incremental data into your business application, if the Source Last Updated Date for the record is an older date or a date in the future, the incremental changes are rejected in the load step. If the Source Last Updated Date is the latest date, the incremental changes to the record succeeds.
For example, if the existing Source Last Updated Date for a record is 16/09/2022 and you update the Source Last Updated Date to 10/09/2022 and import the data, the job rejects the record. If you update the date to a future date and import the data, the job rejects the record. If you update the date to a near future date which is not greater or equal to the current date, such as 18/09/2022, the job imports the incremental changes.
However, you can choose to forcefully import incremental data into your business application irrespective of the last updated date of the source record.
Mapping system-generated fields
Before you map system-generated fields, map the columns from your source file to target business entity fields. Then, map the columns from your source file to the system-generated fields.
The following table describes the system-generated fields that you need to map:
System-generated field
Required
Description
Source Primary Key
Yes
The primary key of a source record.
Population Name
No
Name of the population that you want to use to improve match accuracy. The population accounts for the inevitable variations and errors that might exist in name, address, and other identification data of a particular population.
If you don't map the Population Name field, the default population of the match configuration is used.
NotReadyForMatch
No
Specifies whether to exclude a record from participating in the match process.
If the value is set to True, the record does not participate in the match process. Default is False.
If you don't map the NotReadyForMatch field, the records participate in the match process.
The following image shows the File Import page with mappings of system-generated fields:
Manage mapping
After you verify the field mapping, you can save the mapping for future use. You can save up to 100 mappings at a time. If you have reached this limit, you can overwrite an existing mapping or delete some saved mappings.
Before you import the file, you can preview and verify the mapping.
Note: You cannot save mappings if you import hierarchies.
