Try out your scenarios on two records or field values to see if they work as intended.
Test a Deduplicate Scenario directly from the Scenarios setup page without needing to run a full duplicate search. Enter two records or field values to compare, and verify that the Scenario produces the expected results. If you have more than one Scenario configured, the Scenario Tester will show how they compare using the same records or field values.
- In Deduplicate Setup, configure the Object where you want to check a Scenario.
- On the Scenarios tab, click Scenario Tester
.
The Scenario Tester modal opens. - To try out scenarios on existing records, search and enter two records under Record A and Record B.
Fields used in your scenarios are populated below. Use as-is, or tweak values to see how the scenario responds.
Highlighted rows differ between Record A and Record B.
Alternatively, to see how your scenarios would score certain field values, enter values for one or more fields in the Record A and Record B columns.
- Click Calculate Score
to see how your scenarios match the selected records or field values. -
Scroll down to view the results for each scenario.
The results show the matching score per field, the weight as set in the scenario, and the resulting weighted score.
Match or No Match
The resulting scenario score is displayed as Match 
or No Match 
, depending on whether it reaches the Threshold set in the scenario. Matching scores below the Threshold are considered No Match, and therefore not a duplicate, according to the Scenario settings.
Empty fields
Depending on the scenario's settings, empty fields are included or excluded from the score. This is indicated in the results.
- Empty fields are disregarded: at a row with an empty field value, the scores and weight columns display ‘—’ instead of a value. This indicates that the field did not count toward the total score.
- Empty fields are scored 0% or 50%: a small warning icon is shown next to the 0% or 50% field score, indicating that the values do not actually match for 0% or 50%. Instead, the 0% or 50% score was awarded because empty values get that score according to the Empty Fields setting in the scenario's settings.
