When creating a search index, Duplicate Check creates a key (hash) for every record in your object. The key is created based on fields that are defined in your scenario. Duplicate Check uses this key to compare records. It is advised to create a search index when using custom fields in your scenario, and/or when working with our fuzzy matching methods. Having a search index improves results and scoring of duplicate records.
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 15 records. As a next step, the scenario calculates matching percentages for those 15 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.
You can enable the Duplicate Check Search Index for a certain Object in the *Object* Settings
located on the DC Setup page
The Search Index can be configured in the advanced *Object* Settings
|Search Index with Wild Card
||If enabled, Duplicate Check index search will return partial matches.
|Index Creation for single records
||Determines when the Index creation will start. You can let DC decide when by choosing:
"DC Determines the best option" - Duplicate Check decides when the index is updated.
"Directly. Index is directly available" - The index is updated right away.
"In the background. There is a delay in Index creation" - Index is updated in an apex job, started whenever Salesforce allows it to start.
|Number of records returned in index search
||Decides how many records Duplicate Check returns in the first step of the search procedure. Do not change this, unless you get instructions from our support team.
|Chunk size in Index Creation job
||Determines the chunk size of the index creation job. Do not change this, unless you get instructions from our support team.
||The location where the Search Index will be stored.
Search Index Location
You can choose between two options for storing the indexes. Index Object
Click here to watch a short video of how to enable and create the Search Index.
The default setting is storing the index in the Index Object. When you create a Search Index, the indexes are stored in a custom object called "Index Object". Each record that is indexed takes 2kb of storage space. Within the Object itself
Another option is to store the index in the Object itself. This will store the index in a field in your record, which takes no additional storage space. As a result of updating the record, the last modified date of all records will change.
On the 'Search Index' tab, you can find the 'Create Index' button. After clicking on the button it may take some time before the Search Index is created.We advise creating an index for every Object that you work with. Specifically, when using any custom fields in your scenario, a search index is needed to take them into account.
Please note, that if you choose to store the 'Search Index' in the the same object as the record itself, the last modified date of your record will change. This might trigger workflows you have configured.