The File Paths tab:
- Allows ach user to select where DemandTools Files are saved
- By default, files are saved in the user's "MyDocuments" folder
- A "DemandToolsData" folder is created when the application is installed
- Allows you to change a file location, either type in the new file path or click
on the right and browse for the new location
- If changing a file location, be sure to create a folder for the data using the last subfolder name in the current path and include the \ at the end of the folder name, for example:
- {New Filepath}\Scenario\
- {New Filepath}\MasterRules\
- {New Filepath}\Cache\
- If changing a file location, be sure to create a folder for the data using the last subfolder name in the current path and include the \ at the end of the folder name, for example:
This feature is helpful for allowing multiple DemandTools users to have access to Single Table Dedupe Scenarios and Master Rules, Log Files, Restore Files and ReplaceLists etc. (just change the path to a central network drive).
Users accessing Single Table Dedupe Scenarios and Master Rules from a shared drive do not need full access to the "Scenarios" and "Master Rules" folders (where these files are read from). Users with Read-Only access will be able to read and run the scenarios/master rules, but WILL NOT be allowed to save any changes made to either existing scenarios and will not be able to save any new scenarios.
NOTE: Users will be able to load an existing scenario/master rule and make changes in the user interface. So this will not STOP users from being able to modify existing scenarios and create brand new ones. However, they WILL NOT be able to save them.
1. Restore File Directory
- Where all restore files are saved
- Restore files are created when records are updated via MassEffect, MassImpact, PowerGrid and Reassign Ownership
2. Single Table Dedupe Directory
- Where all Single Table Dedupe scenarios are stored, including pre-built scenarios and any custom scenarios
- Sub-folders are created within this directory to organize scenarios by object
3. Master Rule Directory
- Where all Single Table Dedupe master rules are stored, including pre-built rules and any custom rules
- Sub-folders are created within this directory to organize rules by object
4. Log File Directory
- When a job completes a results screen will be displayed with a count of any errors encountered along with a link to the log file
- If the job completes with errors, refer to the log file as to the source of the errors
- To quickly locate the error in the log file search for "status code"
- One log file is created per day
- The jobs that have been run are timestamped, with the most recent information located at the bottom of the log file
5. Organize Log Files and Restore Files by Salesforce Organization ID
- Unchecked by default
- Will organize files by the Salesforce Organization ID
- Separates Production and Sandbox files, as these have different organization ID's
- Helpful for consultants who may be working on multiple organizations at one time
6. Cache Directory
- Where the MassEffect meta data (object and field definitions) are stored
7. MassImpact Scenario Directory
- Where all pre-built MassImpact scenarios are stored
- Custom scenarios can be stored here also
8. Reassign Ownership Scenario Directory
- No pre-built Reassign Ownership scenarios are provided with DemandTools, but users can save their custom scenarios here if desired
9. Replace List Directory
- Specifies the location of files used with Cleaned Account Name and First Name mapping types, specific formulas in MassImpact, and Filters in PowerGrid
- replacelist.xml
- For use with Cleaned Account Name mapping type
- NameReplaceList.xml
- For use with FirstName mapping type
- ProperCaseOverrides.txt
- For use with ProperCaseName and ProperCaseNameForceAll formulas
- StateMatchOverRides.txt
- For use with StateMatchShort and StateMatchLong formulas
- PowerGridjunkFilter.xml
- PowerGrid Filters saved to this file
- replacelist.xml
