DemandTools 2.91 Microsoft Dynamics Documentation
-
Microsoft Dynamics – DemandTools System Requirements
DemandTools has been designed for and is recommended to be operated on Intel based hardware and Microsoft Windows Operating Systems. Windows 7, 8, 8.1 and 10, Windows Server 2008 R2, Windows Server 2012 Microsoft .NET Framework Version 4.6.2 50...
-
Microsoft Dynamics - Registering the Application
The following instructions describe the configuration steps needed to integrate DemandTools with Microsoft Dynamics 365 as a Native app. Once the application is registered, users will be able to login to the DemandTools applications using the Loc...
-
Microsoft Dynamics - General Settings
1. Auto Login Default setting unchecked Checked - users will be automatically logged in without being prompted for login information All saved login information is stored encrypted in the Windows Registry file on the local machine Au...
-
Microsoft Dynamics - Pre-Built Scenario Summaries
Common Settings for Account, Contact, Lead and Incident (Case) Scenarios Selection of Objects: Use all objects Update Fields where Master is Empty: All selected Combine Field Values: NONE SELECTED Master Rule: Varies by object ACCOUNTS Ri...
-
Microsoft Dynamics - Single Table Dedupe Overview
The Single Table Deduplication module is capable of finding and merging duplicate Accounts, Contacts, Leads and Incidents (Cases). The deduplicator allows for 100% control in terms of how the duplicates are identified and multiple different method...
-
Microsoft Dynamics – DemandTools Login Options
Users have the option to login to a Dynamics production or sandbox instance based on the URL Resource specified. There are 2 options for logging into DemandTools: 1. Using your Client ID / Client Secret2. Using your Client ID and username and pa...
-
Microsoft Dynamics - Scheduled Jobs
Scheduled jobs should only be run by advanced DemandTools users, and only once the job has been thoroughly tested manually. Auto Login and Save Password must be checked on the DemandTools login page for a scheduled process to launch. The Windows ...
-
Microsoft Dynamics – Single Table Dedupe Step 1: Select Table/Records
Step 1: Select Dynamics Entity 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 entity referenced in the saved scenario will lo...
-
Microsoft Dynamics – Single Table Dedupe Step 2: Matching Match Criteria
Specify the criteria to be used when looking for duplicates including the fields to be matched and the desired the matching technique (does not have to be exact matches). When running a pre-built scenario the match criteria is pre-populated but ca...
-
Microsoft Dynamics - Step 3: Grid Control
The total number of matched records/groups is listed in the lower left in RED 1. Duplicate Set Control Expand/Collapse All: Expands/Collapses the duplicate groups Check/Uncheck All: Checks or Unchecks all records Clear All: Unchecks and clears...
-
Microsoft Dynamics - Step 3: Reviewing Results
Step 1: Reviewing Results Grid Field Arrangement Fields selected on Screen 1 are shown at the top of the interface The grid is sorted by the Duplicate Key It cannot be sorted in any other way To locate a specific record use the Find in this ...
-
Microsoft Dynamics - DeDuplication Best Practices & Guidelines
Please test your deduplication scenarios thoroughly before deduping a large number of records, as there is NO automatic "undo"/"rollback" option and NO restore files are created. If you have a Dynamics sandbox, we recommend that you test in this ...
-
Microsoft Dynamics - Mapping Types
Match Categories All - All Categories Alpha - Techniques for text Contact - Techniques specifically for dealing with Contact names CRM - Techniques for Customer Relationship Management Categories Geo - Techniques for address information Internet ...
-
Microsoft Dynamics - Merge Checked Records
Once the records to merge are checked, and the master records determined (either by master rule or manual selection) select Merge Checked Records in the lower right hand corner to begin the merge process. There is no automatic "undo"/"rollback" ...
-
Microsoft Dynamics - Master Rule and Field Rule Validity Check
Master Rule and Field Rule criteria is saved within the scenario file and ALSO saved as separate xml files in the DemandToolsData\Master Rules directory. When loading a saved scenario, an automatic check is done to see if there is a Master Rule o...
-
Microsoft Dynamics - Results Files
Upon completion of the merge, various CSV files will be written out for tracking purposes. These include: MergeRecord File Basic report of the groups that were merged DedupeMergeData File A before image of ALL fields from all the records ...
-
Microsoft Dynamics - File Paths Tab
Microsoft Dynamics - File Paths Tab: Allows each user to select where DemandTools Files are saved By default, files are saved in the users "MyDocuments" folder A "DemandToolsData" folder is created when the application is installed To change...
-
Microsoft Dynamics - DemandTools Installation
Installation takes approximately ten (10) minutes. Before starting the installation, please refer to to the System Requirements to ensure compatibility. Step 1. Install .Net Framework Note: Users will be prompted to install this ONLY if it is no...
-
Microsoft Dynamics - Export Grid Data
The results grid can be exported to a spreadsheet using the Export Grid Data option. When the option is selected there will be 3 types of files that the user can choose to create. Save as Formatted XLS File: Exports to an xls file with all form...
-
Microsoft Dynamics - Pre-Built Master Rules
DemandTools ships with a number of prebuilt master rules for common logic used when selecting master records. These can be used as is or modified as needed. Pre-built Master Rules will be displayed in the upper right-hand portion of Screen 3 - Re...
-
Microsoft Dynamics - DemandTools Options
Options are accessible from either the top menu, Edit -> Options, or the side menu, Preferences -> Options General Settings: Settings for DemandTools as a whole. Click HERE for full details on General Settings. File Paths: Full...
-
Microsoft Dynamics - Field Rules
Field Rules are OPTIONAL. If all fields should be selected from the chosen Master record, then Field Rules are NOT needed. Field Rules allow for an automated field-based custom merge, users pick a master record rule then set up rules for how to h...
-
Microsoft Dynamics - Single Table Dedupe Scenarios
DemandTools ships with a number of prebuilt scenarios to help the user get started. Prebuilt scenarios are saved in the DemandToolsData\Scenario directory. A variety of scenarios ranging from rigid to loose are available providing suggestions as...
-
Microsoft Dynamics - Selecting a Master Record
Each duplicate set needs a master record designation in order to be merged. There are 2 ways to select a master record, manual and automated. Manual Master Selection Double click the pin beside the duplicate record to select it as the master reco...
-
Microsoft Dynamics - Proxy Settings
If an organization uses a proxy server to access the internet, proxy server settings will need to be entered on the DemandTools login screen using the Proxy Setup button in the upper right. Obtaining Proxy Settings Each organization functions d...
-
Microsoft Dynamics - CSV File Options
Default file options that apply to ANY CSV files created by DemandTools 1. CSV Separator: "Comma" (default), "Tab" or type in another desired character as the separator (e.g. |) 2. Encoding: PC's "Default" encoding (default), UTF8, Unicode, ASCI...
-
Microsoft Dynamics - Merge Control Options
Before executing the merge there are a series of options that should be reviewed thoroughly which will affect how the data will be merged. Note: Update Fields Where Master Empty and Combine Field Values will only be shown when NOT using Field Rule...