DupeBlocker Scenario Rules

Scenario rules determine what fields will be used to identify matches, and how the fields will be matched.

All fields that are included in the scenario rules must be populated and must match (based on the mapping type used) for a record to be identified as a duplicate by that scenario.

Multiple Rules are AND'd together, so all fields included in the rules will need to match for the scenario to be triggered.  To OR matching criteria separate scenarios will need to be created with different rules.

For example:  If wanting to match Account Name, Billing Street, Billing City and/or Account Phone:

Scenario 1 with phone:

Account Name
Billing Street
Billing City
Account Phone

Scenario 2 without phone:

Account Name
Billing Street
Billing City

Rule Limits

DupeBlocker limits the total number of scenario rules across all scenarios that apply to a specific object type to a total of 40.

• Account scenario rule count is the total number of rules for all deployed Account and Lead to Account scenarios
• Contact scenario rule count is the total number of rules for all deployed Contact and Lead to Contact scenarios
• Lead scenario rule count is the total number of rules for all deployed Lead, Lead to Contact and Lead to Account scenarios

For example counts would be calculated as follow if all the default scenarios were deployed:



Account scenario rule count = 19
Contact scenario rule count = 20
Lead scenario rule count = 29

Adding a New Rule

To add a new rule click New DupeBlocker Scenario Rule 



Single Object Rules (e.g. Lead, Contact, Account, Opportunity etc.)




1.  Scenario Type:  Will be auto-populated with the Scenario Type as selected on Scenario Details and cannot be updated
2.  {ObjectType} Match Field:  Select the field to match on

• ALL fields EXCEPT long area text and multi-select picklist fields are available for matching, including custom fields

Notes:

• Multi-select picklist and long area text fields are excluded as the keys needed for matching have the potential be too large to support.
• Formula fields can typically be used in matching rules, however the "Full Name" field for Leads, Contacts and Person Accounts WILL NOT work for some reason.  We suspect the problem is due to when/how it gets updated, e.g. DupeBlocker does not see it as "populated" at the time of the insert.  The separate first and last name fields should be used instead of the full name field.  This also allows using custom mapping types on each field individually to improve matching, e.g. First Name Mapping, First XX Letters etc.

3.  Mapping Type:  Select the mapping type you wish to apply to this field

• Mapping types will determine how a field is evaluated as a match
• Various options are available for matching similar field values (e.g. similar Account/Company names, street addresses, phone numbers, first names etc.)
• The mapping types available for selection will vary based on the type of field being matched
• Additional options will be displayed when the First XX Letters/Words or Regular Expression mapping type is selected

• A complete list of available mapping types and detailed description can be found HERE

4.  Scenario:  Will be auto-populated with the Scenario Name and cannot be changed
5.  Additional Mapping Options:  Checking one or more of these options will further loosen the match criteria

• English Fuzzy:  Phonetics engine capable of analyzing words for how they sound when pronounced
  • Through a technique of removing vowels and analyzing the remaining consonants the fuzzy engine works well for matching fields with spelling mistakes
  • Numeric characters are ignored with this option  
  • DO NOT USE for matching phone numbers or other fields that contain numeric characters that you do not wish to ignore (e.g. street addresses)
• Transpose:  Matches all words in a field regardless of their order
  • For example, "Smith and Jones" will match to "Jones and Smith"    
• AlphaClean:  Strips out non-alphanumeric characters  
  • Just look at A-Z and 0-9, & and spaces, ignore everything else
  • Commonly used to ignore punctuation in a field

6.  Match Blank:  By default, blank fields are not matched against each other

• If this option is checked then two blanks fields will be matched

Repeat Steps 1-6 for all fields to be matched on.

Lead to Contact and Lead to Account Rules

With Lead to Contact or Lead to Account Scenarios, a Lead Match Field and either a Contact or Account Match Field will need to be specified.  The Contact or Account Match Field will be displayed as a Related Field in the Scenario Rule.