DupeBlocker Quick Reference Guide

Once installed and configured, DupeBlocker will stop and/or warn end users when they are entering duplicates.  Duplicates can also be auto-merged or auto-converted if desired.

DupeBlocker is designed to work for any SINGLE insert/update to Salesforce, including records inserted/updated directly through the Salesforce user interface and Web to Lead inserts.  It will NOT trigger blocks or warnings for batch inserts/updates (e.g. third party API applications that process inserts/updates in batch mode, Salesforce Data Loader or Import Wizard), but the duplicate keys created to detect duplicates will be kept up to date.

Links to Documentation:

• DupeBlocker Install **Read entire install document PRIOR to installing DupeBlocker
• DupeBlocker Settings
• DupeBlocker Documentation
• DupeBlocker Initial Configuration- Lightning
• DupeBlocker Initial Configuration- Classic

Links to Training:

• DupeBlocker Overview
• DupeBlocker Training
• DupeBlocker Match on Insert Actions Tutorial

Links to Additional Articles:

• DupeBlocker Scenarios
• DupeBlocker Scenario Details
• DupeBlocker Scenario Rules
• DupeBlocker Scenario Filters
• DupeBlocker Scenario Keys

Tips:

If your records are not being flagged as duplicate by DupeBlocker, check to ensure that a rebuild isn’t needed, DupeBlocker is enabled and the scenarios are deployed

• Actions that Trigger a Rebuild:
  • Scenario Changes
    • Scenario is initially deployed/redeployed
    • Scenario Rules (matching criteria) are updated, deleted or added
    • A Scenario "object" Filter is added or updated (not required when adding a "current user" filter)
  • General Changes
    • Anytime changes are made to Clean Account Name Settings, FirstName, State or Country Mappings in DupeBlocker Settings
      • ONLY scenarios that included the related mapping type in scenario rules will be flagged as needing an update
  • Re-enabling DupeBlocker
  • Upgrading to a new version