The Identify Duplicates Match Action allows for the identification of duplicates without automatically applying any actions to those records.
The only parameter required when configuring this match action is a threshold specifying how equal objects have to be in order to be identified as possible duplicates.
For more information on configuring a matching algorithm with this match action, see the Configuring Matching Algorithms Overview documentation here.
When a matching algorithm configured with this match action is applied, the possible matches can be inspected from the matching algorithm object.
If two objects are manually confirmed as being duplicates, a reference will be created between them. The existence of such a reference means that regardless of how the objects are modified, the matching algorithm will always see them as duplicates. The reference type configured as the 'Duplicate Type' on the matching algorithm is used in this case.
Similarly, possible duplicates can be rejected, creating a reference between them. With such a reference, the two objects will never be identified as duplicates by the matching algorithm regardless of how they are modified. The reference type configured as the 'Non-Duplicate Type' on the matching algorithm is used in this case.
In both of the above cases the references can be manually removed via the 'References' tab of the object in question.
If two objects are confirmed duplicates, it is possible to manually merge them into a single object. When performing a merge, you can decide which object will survive the merge and what data that object will inherit from the object being deleted.
For more information, see the Handling Potential Duplicates documentation here.
2018, Stibo Systems