Dedupe Merge Management - Exclude records from merge question

[BillScott]

Hi, I am seeking to set up an automated dedupe process for contacts. In this scenario, when arriving at the Review Duplicates screen, there is a *key field* we are using for scoring.

1.) If the key field isn't populated on any matched (potential merge) records, other scoring will decide the record winner.

2.) If the key field is populated on just one match record but not on the other(s), then via Winner Rules/scoring, the record with the key field populated will be the winner.

3.) However, if two or more matches have the key field populated, no matter the scoring, we want to remove those records from the match results (e.g., we don't want to merge those in any case, or at least they will require a manual inspection).

It seems 1 and 2 are covered with my existing scenario but is there a way via "Filter Match Results" to remove records that meet scenario three?

Or, if this will require two different scenarios, I'd appreciate advice on that path as well. That is, a scenario that excludes any record (via Record Selection Criteria) with the key field populated, then another scenario to handle 2.) and 3.) as per the above. The main requirement being that this will be an automated process for 1.) and 2.) but no action taken for 3.).

Thanks in advance!

[Pugs_Validity · Accepted solution]

@BillScott - This is a fun one. The best way to do this is going to be running Dedupe in two scenarios, back to back.

Key Field is Blank Condition Scenario - We'll want to first merge all matches that do not have the Key Field populated. We'll condition on these records in Step 1.[I used Case Count as my Key Field below, but depending on our Key Field, we'll set it to is Blank/Null/Empty/Etc.]

Our Winner Rule for this run will be just the scoring logic you want to use when there is no Key Field to consider. Once we've processed these merges, we'll be left only with instances where at least one record has the Key Field populated.  

Key Field is Populated Winner Rule Scenario - Next, we'll want to run the Dedupe scenario again, removing the "Key Field is not populated" condition from Step 1 this time. Our Winner Rule on this scenario will be set to Key Field is Populated as 99 with a Score Delta of 1. If both records have the Key Field populated, they'll both score 99 and the Score Delta will prevent them from being merged. There are no instances at this point that neither record has the Key Field field populated. Everything that has multiple records with a populated Key Field will have a tie and not merge. Everything else will have only one record with a score of 99 and a Winner being declared. 

Score Delta - A score delta is the minimum difference between the two top scoring Winners required to select the highest scoring one.

When scheduling this to run, we can select both Dedupe scenarios, running the Key Field is Not Populated Condition scenario first, followed up by the Key Field is Populated Winner Rule scenario. 

[BillScott]

Hi @Pugs_Validity , thanks for the reply and the solution!