Warnings should be reviewed on a regular basis to avoid high Salesforce storage usage and running the risk of exceeding APEX governor limits when inserting/updating records that trigger DupeBlocker scenarios.
- If the records are confirmed as duplicates they can be merged from the warning
- Warnings will automatically be deleted when all the potential duplicates are merged/converted
- More information on merging/converting from a warning can be found HERE
- If the records are NOT duplicates, the warning should be manually deleted
- Select the delete button from within the warning to manually delete
- Deleting a warning will also delete all warning tasks and DupeBlocker Potential Duplicates related lists that pertain to that warning
- By default, only System/DupeBlocker Administrators will be able to delete warnings
- 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
Regular review of Warnings will also help identify scenarios that may be matching too loosely (lots of non-duplicates detected) and/or identify bad data that results in lots of records matching in the SAME warning (e.g. generic required field placeholders like [not supplied] or unknown@unknown.com). DupeBlocker Filters can be used to filter out bad data from triggering a scenario.
Monitoring from the DupeBlocker Applications Tab
System/DupeBlocker Administrators can monitor current warnings from the DupeBlocker Application tab. Select "All" from the view menu to review all active warnings. Views are available for specific objects, e.g. "Account Duplicate Warnings". Custom views can be created if desired.
Although the "Edit" option is visible to System Administrators, DupeBlocker Duplicate Warnings should never be manually edited.
Monitoring for a Particular Scenario
The related list of active warnings is included on the DupeBlocker Scenario page layout.
DupeBlocker Statistics in scenario details also note how many current active warnings there are for this scenario along with a count of the number of potential duplicates associated with those warnings.
Monitoring via Dashboards/Reports
The DupeBlocker Application also comes with a Dashboards and Reports tab for monitoring scenario effectiveness.
The "Largest Duplicate Warnings" report can be used to identify warnings with LOTS of potential duplicates which could be a sign of matching too loosely or bad data that should be deleted or filtered from triggering the scenario.
DupeBlocker Dashboard
DupeBlocker Reports
The following reports are used to populate the Dashboard. Reports can be customized and/or additional reports created.
Monitoring from the Object Record
There are 3 ways to access warning directly from the record that triggered the duplicate:
- The DupeBlocker Potential Duplicates Lightning Component
- Available in Lightning ONLY starting in version 3.10
- The DupeBlocker Potential Duplicates Related List
- Best for viewing duplicates as a related list in Classic
- Inline Duplicates List
- Available for BOTH Lightning and Classic
All are optional but can be added to the object page layouts if desired. Instructions for for adding any of these can be found here.
DupeBlocker Potential Duplicates Related List
- Lists THIS record as a potential duplicate to other record(s)
- Click the warning to show ALL the potential duplicates
- Either delete the warning (not duplicates) or merge/convert from the warning
Inline Duplicates List
- Lists ALL records that are duplicates to THIS record
- Click the warning to show ALL potential duplicates
- Either delete the warning (not duplicates) or merge/convert from the warning
- More information on Inline Duplicates List can be found here
DupeBlocker Potential Duplicates Lightning Component
- Lists ALL records that are duplicates to this record on the Lightning Page Layout
- ONLY AVAILABLE in Lightning (not in Classic)
- The new component is similar to Salesforce's Lightning component used to check for duplicates when Duplicate Management is enabled. We recommend removing Salesforce's component and replacing it on the Lightning page with ours.
- More information on this component can be found HERE
More information on Merging/Converting duplicates can be found HERE.
