QUESTION:
I've set up my scenarios, but for some reason, duplicates are not being detected, what am I missing?
ANSWER:
There are a number of reasons that could be causing duplicates to not be detected including incomplete initial setup of DupeBlocker, misunderstanding of how matching rules are evaluated when looking for duplicates, and customization's that affect more than one object at a time in a single APEX batch (e.g. Standard Salesforce Lead Conversions, Non-Profit Starter Pack, and custom triggers).
Setup issues that could be causing the problem
1. Is DupeBlocker deployed?
- To check this go to Setup->Create->Objects and confirm that all the objects with a name that starts with "DupeBlocker" have the "Deployed" checkbox on the right selected.
2. Is the Scenario, that you think should be triggering the match, deployed, and have the duplicate keys been built?
- Look at the Scenario Details and see if the "Deployed" box is checked and the "Rebuild Needed" box is unchecked. If the Rebuild Needed box is check for deployed scenarios, you will need to Rebuild Keys in order for your scenarios to work properly.
3. Has the trial or purchased license expired?
- To check, go to the DupeBlocker Today page and look in the upper left corner for "License Expiration Date." Click Update.
4. Does the user who created the duplicate have access to the existing record that "should have" been seen as the duplicate?
- To test, turn on the Bypass Security option on the scenario that should be catching the dupes, create another matching record to see if the record is identified as a duplicate.
More information on the Initial Configuration of DupeBlocker can be found here.
Matching Rule issues that could be causing the problem
1. Are ALL the fields included in the matching rules POPULATED on all the records expected to be flagged as duplicates?
- If the scenario is matching on First Name, Last Name, Email, and Phone Number all 4 of those fields need to be populated on all of the records.
- The Rules are AND'd together not OR'd.
- Scenarios can include a "Match Blank" option, which will match a blank to a blank for a particular field, but "Match Blank" WILL NOT match one record with data to one that is blank.
- To do the latter, a scenario needs to be built WITHOUT matching on that field.
2. Should the field match based on the applied Mapping Type? For example:
- If matching on Phone Number and Record A has "(800) 555-1212" and Record B has "+1 800-555-1212", they would ONLY be considered a match if "Relaxed NA Phone Match" was used.
- "Exact" or "Numeric" would not consider these 2 phone numbers to be a match.
- "Numeric" only ignores all punctuation, but not the leading 1.
- If matching on First Name, and Record A has "John" and Record B has "John B.", they can be considered a match if "First XX Words" is used.
- "Exact" or "First Name", even combined with the optional mapping option "Fuzzy" would not consider these a match
- "First Name" is based on common nicknames, e.g. John to Jonathan, and "Fuzzy" adds a phonetic match, but "jn" and "jnb" (the fuzzy interpretation) do not match.
- If matching on Account or Company Name, and Record A has "Huffy Corporation" and Record B has "Huffy Bicycle Corporation", they would only be considered a match if "First XX Words" is used.
- "Exact" or "Cleaned Account Name" would not consider these a match (unless Bicycle had been added to the Account Name Filtering list as a common suffix - which is unlikely).
More information on Scenario Rules can be found in can be found here.
More information on Mapping Types and Options can be found in can be found here.
Lead Conversions (Contact/Opportunity Scenarios not triggering)
Lead conversions affect two objects at the same time and DupeBlocker can only trigger for the first object affected which is the Account Object. Therefore, the creation of a new Contact/Opportunity or update of an existing Contact/Opportunity WILL NOT trigger the Contact/Opportunity Scenarios when a Lead is converted. The only workaround would be to create custom code for Lead conversions and use an asynchronous (@future) call when inserting/updating the Contacts after the Account insert/update is processed.
Non-Profit Start Pack Template (Contact insert duplicates not being detected)
Are you a not-for-profit using the NPSP template and duplicates are NOT being detected for Contact inserts?
Please refer to the following article from our Support Portal for more information:
Custom Trigger on the Object Being Checked for Duplicates Affecting Multiple Objects
If after reviewing all of the above possibilities none seem to explain/resolve the issue then the problem is likely due to a custom trigger on the object being checked for duplicates that is attempting to insert/update multiple objects in the same Apex batch.
Please refer to the following article from our Support Portal for more information:
Reminder
DupeBlocker is designed to work with data that is created or edited one record per API call. If your data is being entered in batch, i.e. more than one record per API call, it will not be dupe checked by DupeBlocker.
