The import details include statistics and settings for the preimport processes, either before or after the actual import process has run. If you are updating the import batch and have run only the preimport processes, you can submit the batch for the actual import process, and rerun the preimport processes if you modified any of the settings.
View the number of duplicate records and duplicate sets that batch de-duplication has identified. If a selected action is to keep one record, based on creation or update date, then only one record from each duplicate set is imported.
You can also view the output from the Import Batch De-Duplication report, which displays all the records that are identified as duplicates, sorted by duplicate sets for parties, addresses, contacts, and contact points.
Each record has a status of either I for insert, or D for duplicate. If the action is Remove All Duplicates, all the records in a duplicate set would have the D status. Likewise, for the Keep All Duplicates action, all records have the I status. For any other action, all records in a duplicate set have the D status except the one record to be imported, with the I status.
If you are updating the import batch and previewing import details after running only preimport processes, you can still modify the actions to take on duplicates. If you change the action from Remove All Duplicates to any other action, then when you submit the batch and rerun batch de-duplication, those records originally marked for removal are:
Sent through Registry de-duplication, if that process is selected.
Checked for other validations and marked for either insert or update.
See:
The address validation statistics include the number of address records that:
Passed or failed validation.
Were sent to be validated by the specified adapter. Not all records in the batch are always validated. See: Details on Actions to Take on Duplicates.
See: Address Validation.
View the number of records from the import batch that Registry de-duplication has categorized, as well as the default action to take on each record type. This table describes the record types and the default actions to take on each type.
| Record Type | Record Type Description | Entities | Default Action | Action Description |
|---|---|---|---|---|
| New and Unique | Does not match any record in the TCA Registry. | All | Insert | Insert the interface table record as a new record in the TCA Registry |
| Existing | Exactly matches a TCA Registry record. | All | Update | Update the existing TCA Registry record with the interface table record |
| Possible Duplicates | Is a potential duplicate of at least one Registry record. The record's match score exceeds the match threshold of the match rule used for the de-duplication, but not the automatic merge threshold. | Parties, party sites, contacts, and contact points | Manual Merge | Insert the record and then include it and its duplicates in a System Duplicate Identification batch for manual merge consideration |
| Duplicates | Is a definite duplicate of at least one Registry record. The record's match score exceeds the automatic merge threshold of the match rule.
Note: This record type is only available if the match rule is enabled for Automerge. | Parties |
| Auto Merge: Insert the record and then automatically merge it with its duplicates |
Note: An interface table record with the Existing type has the same source system and source ID as the corresponding TCA Registry record. The two records also match, as determined by the selected match rule. A record that is a duplicate or potential duplicate also matches TCA Registry records, but does not have the same source system and source ID.
If you are updating the import batch and previewing import details after running only preimport processes, you can still modify the actions to take. Not all actions are available for every record type. Aside from the actions described in the table above, the Remove action is also available for all record types, for removing the record from the batch and not importing it at all.
See: Registry De-Duplication.