How You Manage Duplicates

You can identify potential duplicates in your database by creating and running duplicate identification batches. These batches, when complete, contain sets of two or more potential duplicate records, which are identified by the application for your review.

You can analyze each of these duplicate sets and determine whether you want to resolve them by creating a merge or link resolution request.

While managing duplicate sets you can:

• Use the Test Merge duplicate resolution request type to test your merge configurations, such as survivorship rules and agreement rules, without any impact your application data.

• Resolve duplicates within each identified duplicate set through a merge or link request. A merge request combines duplicate records and a link request joins duplicate records. You can also create a generic request to select the resolution later.

• Remove records that you don't want to include in the duplicate resolution request. You can also restore the previously removed records back to the set from the removed records table.

• Mark a pair of records as nonduplicate, so that these records aren't identified as potential matches. You can remove the pair from the nonduplicate list by changing the end date.

• Change the master record.

• Submit the duplicate sets as merge or link requests for resolution.