Take an example a company uses Salesforce CRM in their organization where users deal with contacts on day to day basis. A user has come to you with request that users should not be able to create records if email entered is already present in the system. How can this be done using DupeBlocker?
What is DupeBlocker?
It is a third party application used in real time for deduplication. It is completely built on force.com platform. This app can be downloaded and installed from AppExchange in Salesforce. DupeBlocker can be installed on Unlimited, Enterprise or Developer edition. Once the app is installed and configured in the Salesforce it will warn users about the duplicate records being created in the Salesforce. You can configure DupeBlocker for standard objects (Accounts, Contacts and Leads) and custom objects. You can also merge or convert the duplicates as desired. DupeBlocker app is displayed in the app menu after it is installed in the salesforce.
App Menu (DupeBlocker) > DupeBlocker Scenarios > New
Now we have to configure the scenario for the DupeBlocker.
Enter the following information
Scenario Name: Enter the scenario name (Contact Email)
Scenario Type: Select the type (Account, Contact, Lead, Lead to Contact and Lead to Account and enabled Custom Objects). This can be done by enabling specific custom object in DupeBlocker settings.
Match on Insert Action: Select how duplicates created via an insert should be handled.
Match on Update Action: Select how duplicates created via an update should be handled.
Create Task for Warning: When you are creating or updating any record this option will give warning and will be flagged as Report Duplicate. We have 4 options to create warning task to notify the Current User, Scenario User or both “Current and Scenario User”. When the duplicate is detected a task reminder is triggered. You can disable the reminder in DupeBlocker Settings.
Deployed: If this check box is not selected then the DupeBlocker will not prevent duplicates and will not warn the users about the duplicates being created.
Bypass Security: If this check box is selected then the DupeBlocker will ignore the sharing rules created in the salesforce.
Enable Dual Filters: When selected the scenario will use different set of filter. If this options is not selected it uses the standard filters.
Person Account Scenario: Enable this option if you are using Person Accounts in the salesforce.
Rebuild Needed: When this check box is not selected then all the keys are up to date. Hence no action necessary.
DupeBlocker scenario detail page created.
Now we need to create DupeBlocker Scenario Rules.
DupeBlocker Scenarios Rules > New DupeBlocker Scenario Rule
Contact Match Field: Select the field on which you want to match for duplicates.
Mapping Type: How you want to match the above selected field.
English Fuzzy: When selected it converts the field to English phonetic equivalent for matching.
AlphaClean: When selected it will remove all the non-alpha-numeric characters.
Transpose: It will match all words in the selected field regardless of order of the words.
Match Blank: If this check box not selected then it will match the blank fields. But if selected then will match with blank field as duplicate field.
DupeBlocker Scenario Rules has been created.
Now let’s test the rule. Create a new record in Contact Object and enter the email in the email field. As soon as we save the record duplicate warning pops up as configured in the DupeBlocker Scenarios. You can also use other options where the system does not allow to save fields with duplicates values.