HelpConsole 2008 SP3.1 - DupeBlocker 2

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

Managing Scenario Keys

Overview

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.

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

Actions that will require keys to be rebuilt:

A Scenario is redeployed
Scenario Rules (matching criteria) for a scenario are updated or new rules added
A Scenario "object" Filter is added or updated (not required when adding a "current user" filter)
Anytime ANY of the DupeBlocker Settings are updated, even if advanced mapping techniques that utilize these lists are NOT selected in the matching rules

A flag is displayed in the scenario detail indicating when a rebuild is needed. The date of the last rebuild is also displayed.

Keys can be built for all scenarios at one time, or on a scenario by scenario basis.

To rebuild all scenario keys, click on the DupeBlocker Scenarios tab, select the View for * All * scenarios, check all scenarios, and click the Rebuild Scenario Keys button.

To rebuild keys for an individual scenario or selected group of scenarios, simply check the box next to the specific scenario(s).

The following status box will be displayed while keys are being rebuilt.

Keys can also be rebuilt from within a scenario by clicking the Rebuild Keys button. There is also an option to Rebuild All Keys in this same screen. If this option is selected, keys will be rebuilt for all DupeBlocker scenarios.

When existing rules (matching criteria) for a scenario are updated or new rules added, 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.

How Long Will it Take?

The amount of time required to rebuild keys will depend on how many records are in each table. Keys are built at the rate of 50k/10 minutes for standard high speed internet connections. For example, when rebuilding keys for a Contact table that contains 200,000 records a rebuild will take approximately 40 minutes.

Note: This is just an estimate, times will vary based on the actual internet speed, the internet browser used, and number of scenarios for the particular table. Using Mozilla or Safari as a browser seems to complete key builds about 30% faster than Explorer.