DupeBlocker - How to test a DupeBlocker Scenario WITHOUT building Keys

Key building can be a time-consuming process for orgs with high data volume. So, it is important to be able to test DupeBlocker Scenarios without going through a complete key build after each qualifying change or after initial creation/deployment. 

• Click here to learn which actions force a key rebuild to be needed.

DupeBlocker keys records when they are created and edited. This makes it possible for a user to quickly test the scenario’s efficacy and proper setup.

Steps to test a Scenario marked as needing a rebuild:

1. Create a DupeBlocker Scenario
2. Go to an existing record you want to test with and click Edit and Save
   1. Existing records are keyed when they are modified and saved. This record has now been keyed for all deployed DupeBlocker Scenarios for this object type.
3. Create a New Record that matches the record from Step 2 based on the settings (matching rules and filters) of the DupeBlocker Scenario created in Step 1.
   1. New records are keyed when they are saved. This record has now been keyed for all deployed DupeBlocker Scenarios for this object type.
4. If the test is successful, the record created in Step 3 will have the scenario match on insert action applied (block/merge/report).