Scenarios

This article is also available as a How-To video. Watch now!
Duplicate Check uses scenarios to identify duplicate records in Salesforce. By adjusting the existing scenario, you can decide yourself based on what fields and what logic Duplicate Check should compare your records. In addition, define yourself what should be considered as a duplicate record.  


Edit name



By clicking the pencil icon behind the scenario name, you are able to edit the name. The icon will only be visible when you move your mouse over the scenarios name.


Threshold

In the process of comparing records, Duplicate Check calculates a matching percentage. That percentage is calculated by comparing the values of the fields that are defined in your scenario. The Threshold level decides from what percentage a match is defined as a potential duplicate record. The standard setting is 75%. Every score that is equal to, or higher than 75% will be defined as a potential duplicate record. As a result, a match between two (or more) records can deviate with a maximum of 25% in its values.
 
By setting the Threshold level at, for example, 100%, the scenario will only return results that have an exact match on the fields that are defined in your scenario*.
Fields

The fields that are defined in your scenario are the fields that we are comparing between records. Your scenario is a strategy on how to compare records and find duplicates. The fields defined in the scenario are the fields that are used to compare records. The Lead Default scenario (standard configuration) uses the First Name, Last Name, Company Name and Phone field. You can remove fields from your scenario by clicking the 'delete' icon at the end of the table. Adding a new field is easy, just click the 'Add new field' button.

Matching method

A matching method is a (fuzzy) algorithm that we use to analyze field values. Because every field has a different type of value (e.g. a numeric vs. text), it is important to apply a matching method that is able to analyze that certain value type. The matching method also decides if you apply an exact or fuzzy logic (e.g. detecting spelling mistakes) or not. Find out more about matching methods in this article.

Empty fields

In most databases, records are not always populated at all fields. The empty fields setting lets you configure how to handle empty fields in the comparison process. You can choose between three options. 

Depending on your 'empty fields' setting, your scenario could calculate a 100% score based on one field, even if there are more fields defined in your scenario.

Empty Field options: 

Disregard
 
“Disregard” will not take into account empty fields when calculating a matching percentage and can still trigger a 100% score if there are one or more fields without value. Using this setting, we allow you to find duplicate records that are not entirely filled out. "Disregard" can however also trigger false positives. If so, please check out the other setting options. These example scores are calculated with an equal weighting for all fields. Learn more in this article.

First Name Last Name Company name Email Address Phone number Score
Jennifer Blake Laoreet Coorporation j.blake@loareet.com 1-817-297-7931 100%
Jennifer Blake Loareet Coorporation Empty 1-817-297-7931  

Or..

First Name Last Name Company Name Email Address Phone Number Score
Jennifer Blake Laoreet Coorporation j.blake@laoreet.com 1-817-297-7931 100%
Jennifer Empty Empty Empty Empty  


Score 50%

Instead of disregarding empty values, “score 50%” will take into account empty fields for 50% in the calculation process. As a result, the matching percentage is lower.
First Name Last Name Company name Email Address Phone number Score
Jennifer Blake Laoreet Coorporation j.blake@laoreet.com 1-817-297-7931 92%
Jennifer Blake Laoreet Coorporation Empty 1-817-297-7931  


Score 0%

“Score 100%” will take into account empty fields for a full 100%. As a result, the difference between the two email values is considered as a non-match. The matching percentage will be lower.
First Name Last Name Company Name Email Address Phone number Score
Jennifer Blake Laoreet Coorporation j.blake@laoreet.com 1-817-297-7931 80%
Jennifer Blake Laoreet Coorporation Empty 1-817-297-7931  


Apply to

Decide to which feature of Duplicate Check for Salesforce you want to apply the search scenario. You can choose any number of features.


Manual insert Prevention
Manual Update Prevention
DC Search
DC Convert
DC Check
DC Entry
DC Live
DC Job
Unique Import / API Bulk Insert
API Single Insert / Update
DC Apex API
Web To Lead
Data API

Weighting

Use the weighing setting to decide what fields should weigh the most when comparing records. A field with a higher weight, has more impact on the matching percentage than a field with a lower weight.

Example 1: Weighting equal to all fields

Field Matching Method Weighting
First Name Exact 10 (10/50 = 20%)
Last Name Exact 10 (10/50 = 20%)
Company Exact 10 (10/50 = 20%)
Email Exact 10 (10/50 = 20%)
Phone Exact 10 (10/50 = 20%)

First Name Last Name Company Name Email Address Phone Number Score
Jennifer Blake Loareet Coorporation j.blake@loareet.com 1-817-297-7931 80%
Jennifer Blake Loareet Coorporation different@mail.com 1-817-297-7931  

Example 2: More weight on Email Address

Field Matching Method Weighting
First Name Exact 10 (10/60 = 16.6%)
Last Name Exact 10 (10/60 = 16.6%)
Company Exact 10 (10/60 = 16.6%)
Email Exact 20 (20/60 = 33.3%)
Phone Exact 10 (10/60 = 16.6%)

First Name Last Name Company Name Email Address Phone Number Score
Jennifer Blake Laoreet Coorporation j.blake@laoreet.com 1-817-297-7931 67%
Jennifer Blake Laoreet Coorporation different@email.com 1-817-297-7931  
 

Having trouble?

Our support agents are ready to help you !