Single Table Dedupe - Step 1

Select Object/Records to Dedupe

1:  Select Salesforce Object to Dedupe or Load Scenario

Manual Object Selection

Use this option when creating a scenario from scratch.  If loading a saved scenario this step can be skipped, as the object referenced in the saved scenario will load automatically along with the other saved scenario settings.

• Select the object to de-duplicate in the Salesforce object to dedupe drop down box and click Use Object
• Proceed to Step 2:  Select Field to Show on Found Duplicates Grid

There is no NEW scenario button.  To build a custom scenario simply pick the desired object in the Select object to dedupe box, build the scenario on the various screens and then Save Scenario. If saved in the DemandToolsData\Scenarios folder scenario it will show in the list of scenarios on the left.  A new folder will be created if there were no existing scenarios for a particular object.

Show Portal Users Checkbox (for Contact Scenarios) 

If Contacts are selected as the object to be deduped, there will be a Show Portal Users checkbox just to the right of Use Object.  When checked, the Contact Full Name for the portal user will be highlighted in purple in the results grid for easy identification when manually picking a master record.  Salesforce will NOT allow a portal contact to be deleted, therefore portal contacts always need to be selected as the Master Record.

A Master Rule, Portal User, is also available to aid in merging Contacts.

More information regarding issues with merging portal enabled contacts can be found in the following Salesforce Help and Training link.

Scenarios

DemandTools ships with a number of pre-built scenarios to help the user get started.  Pre-built scenarios are saved in the DemandToolsData\Scenario directory.  A variety of scenarios ranging from rigid to loose are available providing suggestions as to which fields typically should be selected for matching and suggested mapping types to be used with those fields.  It is recommended that each user review the scenario they choose prior to running and if desired modify to fit their data needs.  All scenarios are stored locally on the users PC in the DemandToolsData\Scenarios directory will automatically be loaded into the Single Table Dedupe user interface for use. Detailed descriptions of all the prebuilt scenarios that ship with DemandTools can be found HERE.

Users can also opt to create their own scenarios completely from scratch.  User created scenarios can be saved and loaded from any Windows directory, however, only those saved in the DemandToolsData\Scenarios directory will be displayed in the user interface.  To load a scenario that was saved elsewhere, simply use the browse option to browse to the appropriate folder.

1. All Scenarios are listed in the left hand column
   • Click the icon to the left of a folder to list all scenarios for that object
2. When a scenario is highlighted the center portion of the screen displays an overview of the scenario
   • Single click to show the overview of a scenario
   • Double click to load a scenario
     • Loaded scenario will be highlighted in green
3. The right side of the screen shows the fields selected to view on the found duplicates/duplicate grid
4. Load/Run/Delete Scenario
   • Load Scenario:  Loads all settings of the selected scenario including the saved Master Rule or Field Rule criteria
     • The user can click through all screens manually and make any desired changes before finding results
     • When clicking Load Scenario, the user will be taken to a File Explorer browse window to select the desired scenario 
     • The file path will default to DemandToolsData\Scenarios
     • Can browse to any folder and select a saved scenario
   • Run Scenario: Loads scenario settings, automatically processes each step and applies the master rule to the found duplicates
     • Users will be able to review the results prior to selecting Merge Checked Records
     • Can single click on a scenario shown in the user interface and select Run Scenario
     • To run a scenario NOT stored in DemandToolsData\Scenarios, click on a folder name first then click Run Scenario
     • Will be provided with the option to browse to a different location
   • Delete Scenario: Removes the scenario from the list and deletes the source xml file
     • ONLY works with scenarios displayed in the user interface
     • To delete scenarios NOT saved in DemandToolsData\Scenarios, users will need to browse to the scenario location on the PC and manually delete the STDxml file
5. Save/Clear Scenario Buttons located at the very bottom of all of the Single Table Dedupe Screens
   • Save Scenario: Used for newly created or modified pre-built scenarios
   • Scenarios will be saved in the DemandToolsData\Scenarios directory by default, but users can browse to any location on the PC
   • Clear Scenario: Clears out all selections and allows the user to start over, either by selecting a different scenario or by creating one manually.

Note:  Scenarios created/saved in DemandTools 2.7 or higher CAN ONLY BE LOADED/RUN in DemandTools 2.7 or higher. They are not compatible with earlier releases and will not even be shown in the Single Table Dedupe user interface.  When running DemandTools as a batch process on another PC/Server users will need to ensure that DemandTools 2.7 or higher is installed. DemandTools 2.7 can run scenarios from earlier versions.  If a user accidentally schedules a 2.7 scenario in an earlier version, the scenario will not run and the DemandTools logfile will report "Incorrect extension for scenario".

Click HERE for more information on Single Table Dedupe Step 2