Home > DupeBlocker Step by Step Instructions > Scenarios > Managing Scenario Keys

Managing Scenario Keys

An internal table of duplicate keys needs to be maintained for all Scenarios to function properly. When DupeBlocker is initially installed, keys will need to be built for all deployed scenarios. This includes the default scenarios that ship with DupeBlocker and any new scenarios created from scratch.

Anytime a new record is inserted/updated in Salesforce keys are added/updated, including batch inserts/updates.

Anytime rules (matching criteria) for a scenario are updated or new rules added, or a scenario is redeployed, a rebuild of keys will be needed to accurately detect duplicates based on the changes.  A flag is displayed in the scenario detail indicating when a rebuild is needed.  The date of the last rebuild is also displayed.



More information how to build/rebuild your keys can be found in DupeBlocker Basics -> Initial Configuration of DupeBlocker -> Building Scenario Keys.

See also