Batch De-Duplication

Batch de-duplication identifies and resolves duplicates within the batch that you are importing from the interface tables. You cannot check for duplicates between batches in the interface tables.

If you select to run batch de-duplication, you must:

For example, Organization 1 and Organization 2 are found to be duplicates. You selected to keep the record with the earliest creation date, which is Organization 1. Organization 1 is now a unique record, but it has five duplicate addresses. Those addresses are resolved based on the selected action to take on duplicate addresses.

Details on Actions to Take on Duplicates

The possible actions to take on duplicate parties and child entities include keeping one record based on creation or update date. Entering the most recent update date in the interface tables, however, is not mandatory. If none of the records in a set of duplicates has a date, then the one record to be imported is randomly selected. If only some of the records have a date, then the record to be imported is selected only from records that have a date, based on the specified action.

The action you select for duplicate parties affects address validation. If you select to update the batch and preview preimport process results, then address validation checks all addresses in the import batch, regardless of the selected action for duplicates. When you preview the results, you can still change the action to take.

If you choose to import directly, without a preview, then address validation checks only addresses that are imported, not those that are removed based on the selected action. See: Address Validation and Import to Registry.

Related Topics