Classic
DupeBlocker Classic can be implemented in 3 easy steps:
1. Go to the DupeBlocker Settings tab to load the default scenarios and review the default settings, making changes as necessary.
- The DupeBlocker Settings allow for customizing various matching options, enabling non-standard objects for matching (e.g. Opportunities, Assets, custom objects etc.), and configuring other key features.
- More information on customizing the DupeBlocker Settings can be found HERE.
- Note: The DupeBlocker Settings tab needs to be accessed to load the default settings and begin duplicate detection. Even if no customizations will be done to the supplied settings, this tab still needs to be accessed to complete the initialization of DupeBlocker.
2. Go to the DupeBlocker Scenarios tab and review the default deduplication scenarios. Update, deploy and/or create new scenarios to suit your organizations needs.
- DupeBlocker ships with two standard matching scenarios for Accounts, Contacts, Leads and Lead to Account and Lead to Contact matching. These can be used as is, customized and/or deleted to accommodate your specific needs.
3. Rebuild the scenario keys for all deployed (activated) scenarios. This is done by opening a scenario and clicking Rebuild All Keys.
Lightning
DupeBlocker Lightning can be implemented in 4 easy steps:
1. Go to the DupeBlocker Settings tab to load the default scenarios and review the default settings, making changes as necessary.
- The DupeBlocker Settings allow for customizing various matching options, enabling non-standard objects for matching (e.g. Opportunities, Assets, custom objects etc.), and configuring other key features.
- More information on customizing the DupeBlocker Settings can be found HERE.
- Note: The DupeBlocker Settings tab needs to be accessed to load the default settings and begin duplicate detection. Even if no customizations will be done to the supplied settings, this tab still needs to be accessed to complete the initialization of DupeBlocker.
2. Go to the DupeBlocker Scenarios tab and review the default deduplication scenarios. Update, deploy and/or create new scenarios to suit your organizations needs.
- DupeBlocker ships with two standard matching scenarios for Accounts, Contacts, Leads and Lead to Account and Lead to Contact matching. These can be used as is, customized and/or deleted to accommodate your specific needs.
3. Rebuild the scenario keys for all deployed (activated) scenarios. This is done by opening a scenario and clicking Rebuild All Keys.
4. Override Salesforce's New/Edit pages with DupeBlocker's custom wrapper page.
- Step 4 is ONLY required if a DupeBlocker Scenario is set to a blocking action (e.g. Do Not Insert, Do Not Update, or Redirect to Existing). The custom pages allow for the the blocking messages to be properly displayed, the Bypass Block button to be shown and for inserts to be redirected to any matching existing records. If "Do Not Update" is NEVER used then only the New button needs to be overridden.
Customization Questions
The Quick Start steps will enable basic DupeBlocker functionality. To take full advantage of DupeBlocker's capabilities, the application should be customized to best fit your organization's needs.
The answers to the following questions will help determine how to customize DupeBlocker and/or Salesforce. Customizing DupeBlocker will likely be an ongoing process. These questions are designed to get you started.
Who will be managing the detected duplicates, standard users, system administrators, or a manager?
- Access to specific DupeBlocker objects may need to be adjusted accordingly (default is read-only for non-admins)
- User profile permissions may need to be adjusted accordingly
- Whoever will be manually merging duplicates from warnings will need to have the appropriate Salesforce permissions to merge records directly in the Salesforce User Interface
Is blocking duplicates from being inserted acceptable, or will just warnings be generated, or a combination?
- If warnings are generated, who will be monitoring the warnings and deciding if the warning should be deleted or if the records should be merged?
- Will tasks be created for warnings to alert someone that a duplicate was detected?
- Who should the task be assigned to, the user who created the duplicate, the scenario owner (e.g. admin or manager), or both?
- More information on managing warnings can be found HERE
Will DupeBlocker be rolled out to ALL users and fire for ALL records of a particular type?
- Filters can be applied to limit which users and or records trigger DupeBlocker
- More information on filters can be found HERE
What criteria (fields) will be used to determine if records are duplicates?
- Every organization's definition of a duplicate is different and ANY field can be used in matching, including custom fields
- Default scenarios are provided with "common" matching criteria, but these are just a baseline
- Multiple matching scenarios can be created per object so consider the different combinations of fields/matching "strictness"
- Stricter scenarios may be set to block
- Looser scenarios set to warn/report duplicates
- More information on scenarios can be found HERE
Are there any automated processes that insert records (single inserts as DupeBlocker will not work with batch uploads)?
- Is Salesforce Web to Lead implemented in the instance?
- More information on customizing DupeBlocker to work with Web to Lead can be found HERE
- Will records be auto-merged or auto-converted?
What objects will DupeBlocker be used for?
- Objects other than Accounts, Contact or Leads will need to be enabled in DupeBlocker Settings
- More information on working non-standard objects can be found HERE
Are Person Accounts enabled in the instance and if so will DupeBlocker be used to detect duplicate Person Accounts?
- 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 HERE
Is there an Apex developer available at the organization that can take advantage of some of the advanced customization features?
- Calling in a Custom Apex Code Class or Custom Visualforce page when duplicates are detected
- Supplying custom unit test data
- Working with the Customer Matching API feature
- More information on these advanced options including sample code can be found HERE
