The load step loads the cleansed records into the MDM SaaS data store. It also generates workflow tickets for records that belong to business entities with configured business events.
If ticket generation fails for any records, the Generate Tickets for Pending Records step creates tickets for them.
If an ingress job fails at this step or the step is in the Running status for a long time, go to the My Jobs page of Data Integration to troubleshoot. If the taskflow is in the Suspended status, view the subtasks and select the failed mapping task. Download the sessions log and check for errors.
If your organization uses basic, advanced, and DaaS rule associations, and rule associations that are created using objective groups, MDM SaaS runs rule associations and objectives during both transform and load steps.
The following table describes the metrics that you can view in the Overview section of the load step:
Metric
Description
Total Records
The total number of records that the step processed.
Error Records
The number of records the step didn't process. An error record might be currently in the approval workflow or contain a relationship mismatch.
Starting Records for Asset
The total number of records that the step processed for a specific asset.
Successful Records
The number of records that are loaded and moved to the index for search step. Number of records that are created, updated, deleted, and restored. The records that are created, updated, deleted, and restored move to the index for search step.
Created Records
The total number of records that are created.
Updated Records
The total number of records that are updated.
Deleted Records
The total number of records that are deleted.
Restored Records
The total number of deleted records that are restored.
You can also view the runtime parameters and metrics for the load step.