In one of the latest releases of Duplicate Check, it's possible to exclude fields from being taken into account in the Search Index. Learn more about when to exclude a field from the Search Index by reading this article.
Duplicate Check uses the Search Index
to find potential duplicate records in Salesforce. This Search Index is a string of values and numbers which is created based on the scenario that you use.
When we search with the Search Index, potential duplicates are returned. By default, we return about 40 records. As a next step, the scenario calculates matching percentages for those 40 records. Every pair with matching percentages that are equal to, or higher than the defined threshold level, are defined as duplicate records and returned in the UI.
When to exclude a field from the Search Index?
In a Salesforce environment with a lot of records, it's important that we search with a Search Index that is as unique as possible. If we search with values that can be found in a lot of records, it's possible that the right duplicate record is not part of the 40 records that we return.
We can, therefore, help Duplicate Check by not taking into account fields with values that can be common in a lot of records. By excluding them only from the Search Index, but not from the process of calculating a matching percentage, it's easier to find duplicate records in environments with a large data volume.
Step 2 Exclude a field in a scenario
At the DC Setup, navigate to the object you want to configure this for. After unfolding your scenario, you see a new column is added called "Do Not Index". Pick a field you want to exclude from the Search Index, and switch the toggle to set it to "true".Please note that the "Do Not Index" column is only visible when the Search Index is enabled.
After making changes to your scenario, make sure to re-run the Search Index.
In the example above, the "Country" field was excluded from the Search Index. This could make sense because a lot of records can have the same value in this field. By excluding it from the Search Index, the field is not used when searching for potential duplicates but is used when calculating a matching percentage.