Home > DupeBlocker Installation > Initial Configuration of DupeBlocker

Initial Configuration of DupeBlocker

Overview

In order to effectively use DupeBlocker minor changes will need to be made to your Salesforce configuration after install is complete and the application is deployed.  In addition, the DupeBlocker Settings will need to be customized to maximize duplicate detection.

Note:  The DupeBlocker Settings tab needs to be accessed to load the default settings and begin duplicate detection.  So, even if no customizations will be done to the supplied settings, this tab still needs to be accessed to complete the initialization of DupeBlocker.

DupeBlocker ships with two standard matching scenarios for each object:  Accounts, Contacts, Leads and Lead to Account and Lead to Contact matching.  These can be used as is, or customized and/or deleted to accommodate your specific needs.

Note:  DupeBlocker will work with Person Accounts, however, additional configuration steps are required to function properly.

More information on special considerations when detecting Person Account duplicates can be found in DupeBlocker Advanced Functions -> Person Accounts.

Customizing Page Layouts

Page layouts will need to be updated to show the "DupeBlocker Potential Duplicates" related list for all Account, Contact, Lead page layouts.  To do this in Salesforce go to Setup->Customize->"Object"->Page Layouts.



It is also recommended that the Related List Layout be updated to include the "Duplicate Warning" and "Scenario" that triggered the Warning.  This will allow the user to go directly to the warning and ultimately convert/merge the potential duplicates.

To do this, while still in edit mode, click on the tool icon for the DupeBlocker Potential Duplicates related list that was just added.  Select "Duplicate Warning" and "Scenario" from "Available Fields" on the left and click "add" to add to "Selected Fields".  Also, uncheck the "New" box under standard buttons.



Customizing Profiles

To access user profiles go to Setup->Administration Setup->Manage Users->Profiles.

Enabling Apex Class Access

Note:  If the instructions are followed in Installation Step#4 for “Choose Security Level” to select “Set All” for non-admin users, this will already be enabled for all profiles.

To verify this go to Setup->Develop->Apex Classes page and click on the “Security” link next to DB_WebServices and confirm that all profiles are enabled.  Add additional profiles as necessary.





DupeBlocker Custom Object Permissions

Starting with Salesforce Spring '10, all standard Salesforce profiles will not have access to the DupeBlocker custom objects and CANNOT be updated to gain access.  In order for users to have access to the DupeBlocker objects they will need to be assigned a custom profile.  Existing custom profiles will be assigned "Read" only access to the following DupeBlocker Objects:

Warnings
Potential Duplicates
Scenarios
Filters
Rules

All non administrator custom profiles added after the installation of DupeBlocker should be updated to have read access to the same DupeBlocker objects listed above.





Note:  Since only "Read" access is granted, if a warning is generated and the user does not wish to merge/convert the potential duplicates, only the System Administrator will be able to delete the warning.  Access can be granted to users to delete warnings, but this could defeat the purpose of DupeBlocker (user chooses to ignore the warning, but the record is in fact a duplicate and should be merged/converted).  Since this can be done based on the specific profile, this option could be enabled for managers but not for general users.

DupeBlocker Settings

To maximize the effectiveness of finding duplicates, review and update the DupeBlocker Settings tab.  DupeBlocker comes with default settings and can be implemented without customization, however to load the default settings this tab needs to be selected one time.  Settings can be updated at any time.

Settings available for customization include:

• General Settings:  Specify the primary e-mail address for DupeBlocker exception/error notifications.  If left blank, the current user will be notified.
• Account Name Filtering:   Rules for matching similar Account names when using the "Cleaned Account Name" mapping type (common punctuation to ignore or standardize, common suffixes and prefixes to ignore).
• Nickname Filtering:  Match a nickname to it's full equivalent when using the "FirstName" mapping type, for example Mike will match to Michael.
• Web Lead Sources:  Specify the Lead Source that is assigned to Web to Lead inserts.  This will ensure that Leads entered via Web to Lead will NEVER be blocked entirely.  More information on Web to Lead can be found in DupeBlocker Advanced Functions -> Web to Lead.
• Country Filtering:  Advanced options for matching countries when using the "Country Match" type.
  

Step 1:  Access DupeBlocker Application

Access the DupeBlocker application from the drop down list in the upper right hand corner of Salesforce.
 


The following DupeBlocker tabs will be displayed:



Step 2:  Select DupeBlocker Setting Tab

Select the DupeBlocker Settings tab to begin customization or load default settings.  It is highly recommended that the Account Name Filtering settings are customized to look for common suffixes that commonly appear in your organizations Account Names.

For example, add "mfg", "manufacturing", "bank", "group", "hotel", "mortgage", "consultants", "hq", "accountants", "llp" etc.

This list is not case sensitive.

Step 3:  Click Setting to be Updated

Click the tab for the settings to be customized.

General Settings: Enter the email address for DupeBlocker exception emails (typically the DupeBlocker Administrator's email address).



Account Name Filtering, Nickname Filtering, Web Lead Sources, Country Filtering:



To add a new value click "Add" in the bottom left corner of the screen and type in the new value.  To remove an existing value, highlight the value in the list and click "Delete".

After customizing select "Save All Settings" in the bottom right.  If "Reload Settings" is selected before saving new additions the following message will appear:



Click "Yes" to delete your most recent additions.  Click "No" to leave changes in place, and then select "Save Settings".

Review/Deploy Default Scenarios

Before using DupeBlocker, default scenarios included with DupeBlocker should be reviewed, updated and deployed as needed.  Default scenarios are marked as undeployed when installed.  New scenarios can also be created to suit your organizations needs.  Scenario keys will need to be built for all deployed scenarios before they can be used.

Details regarding the default scenarios that ship with DupeBlocker can be found in DupeBlocker Step by Step Instructions -> Scenarios -> Default Scenarios.  More information on creating/customizing scenarios can be found in DupeBlocker Step by Step Instructions -> Scenarios -> Creating/Editing Scenarios.

Building Scenario Keys

Once all scenarios are in place and deployed, duplicate keys will need to be built for all scenarios so that duplicates can be identified.  Before building keys refer to DupeBlocker Installation -> DupeBlocker System Requirements for information on Salesforce storage requirements and API calls needed.

Instructions on how to build and maintain keys can be found in DupeBlocker Step by Step Instructions -> Scenarios -> Creating/Editing Scenarios -> Managing Scenario Keys.

See also