This feature helps visualize why certain records were consolidated to a particular record through Build Match Group (BMG) process, which removes redundant matching in advance of the consolidate process. By investigating the rules that originally triggered pairs of records to be matched, you can decide—on a

case-by-case

basis—whether to unmerge consolidated records.

For example, suppose a base object had the following match pairs:

record 1 matches to record 2
record 2 matches to record 3
record 3 matches to record 4

After running the match process, during which the BMG was created, and before running consolidation process was run, you might see the following records:

record 2 matches to record 1
record 3 matches to record 1
record 4 matches to record 1

In this example, there was no explicit rule that matched 4 to 1. Instead, the match was made indirectly due to the behavior of other matches (record 1 matched to 2, 2 matched to 3, and 3 matched to 4). An indirect matching is also known as a transitive match. By displaying the complete match history, you can expose the details of transitive matches.