General Settings - DemandTools V Release

1. Log in to DemandTools and your CRM
2. Click the Gear icon and select General Settings 

Application Settings 

1. Enable Undo Operations

• Applicable to: Dedupe and Modify
• Default setting: checked 
  • Unchecked: Users cannot undo recent scenarios that were run with Enable Undo Operations disabled
  • Checked: Users are allowed to undo recent scenarios that were run with Enable Undo Operations enabled
• Scenarios run while Enable Undo Operations is disabled do not create Restore Log files

2. Show only active users 

• Applicable to: all Modules 
• Default setting: unchecked 
  • Unchecked: All active and inactive users are shown in any lookup/drop-down lists 
  • Checked: Only active users are shown in any lookup/drop-down lists  

3. Show non-standard users 

• Applicable to: all Modules 
• Default setting: unchecked 
  • Unchecked: Only standard users are shown in any lookup/dropdown lists.
  • Checked: show all user types including Partner users 
• Notes:
  • Log out and back in after checking this option to load all users 
  • If there are a lot of non-standard users, this will slow down the login process 

4. Highlight portal users

• Applicable to: Dedupe
• Default setting: unchecked 
  • Unchecked: no highlight for portal users
  • Checked: contacts who are Partner/Customer Portal or Community users will be indicated with a purple highlight on the Full Name field in the Dedupe preview grid
• Notes:
  • Access to the User object in your CRM is required to enable this setting
  • Contacts associated to portal users should be merged with caution and should typically be chosen as the winning record in a Dedupe action
  • Associated winner rule criteria: Record is Portal User
  • Contact Full Name field is non-editable and always visible on the preview grid

5. Allow field truncation 

• Applicable to: Modify, Import, and Dedupe
• Default setting: unchecked 
  • Unchecked: rows with data that exceeds the specified field length in Salesforce will fail with STRING_TOO_LONG errors.
  • Checked: data that exceeds the specified field length in Salesforce will be truncated to fit the specified field length when inserting/updating records. 

6. Create tasks for scheduled jobs

• Applicable to: all scheduled jobs 
• Default setting: unchecked 
  • Unchecked: no tasks created for scheduled jobs
  • Checked: tasks created for all scheduled jobs assigned to the user id of the person who ran the scheduled job.
• Notes:
  • When the user logs into Salesforce after the completion of a scheduled job, an open task with completion information will be shown in their list of open tasks.

7. Send user emails for new/update tasks or leads with assignment rules 

• Applicable to: Import
• Default setting: unchecked 
  • Unchecked: user emails are not triggered for new tasks
  • Checked: user emails will be triggered for new tasks notifying the assigned user that a task was created.

8. CRM timeout 

• Applicable to: all modules  
• Default setting: 2 minutes
  • It can be increased to as high as 10 minutes  
• Notes:
  • This setting is the amount of time in minutes DemandTools will wait for a query to process before timing out.
  • May need to be increased for large queries that are receiving "Error Accessing Data: The operation has timed out." errors as seen in the logfile. 

9. CRM Version 

• Applicable to: all modules 
• Default setting: v51.0
• Notes:
  • Type in the CRM API version your organization is on (e.g. v47.0)
  • Lowering your version may reduce access to functionality 
    • For example, bulk hard delete does not work for any Salesforce API version under 51.
  • Be sure to update this field for each CRM environment if working in multiple CRM environments

Batch Size Settings

Default API

Specify the API batch size, or number of records processed, for the following operations. Each batch uses one API call.

1.  Insert/Update/Delete

• Applicable to: Import, Export, Delete, Modify, and Tune
• Default setting: 100
  • Batch size can be adjusted between 1 and 200 
• Notes:
  • You may choose to lower batch sizes to avoid errors from triggers that have not been optimized to handle batch processing.

2. Merge

• Applicable to: Dedupe
• Default setting: 5
  • Batch size can be adjusted between 1 and 200 
• Notes:
  • Merges can be batched to improve speed of merging and reduce the number of API calls
  • Higher batch sizes may result in Apex code errors 
  • Determining the ideal batch size per object will be trial and error 
  • Instances with little to no custom Apex code can likely increase the batch size and those with lots of Apex code or code that has not been coded to handled batch processing may need smaller batch sizes. 

3.  Lead Conversion

• Applicable to: Convert
• Default setting: 10
  • Batch size can be adjusted between 1 and 100 
• Notes:
  • Conversions can be batched to improve speed of merging and reduce the number of API calls. 
  • Higher batch sizes may result in Apex code errors 
  • Determining the ideal batch size per object will be trial and error 
  • Instances with little to no custom Apex code can likely increase the batch size and those with lots of Apex code or code that has not been coded to handled batch processing may need smaller batch sizes.

Bulk API

Use the Bulk API to process more records per API call. Adjust performance by customizing how many records will be processed per batch. To enable, select the Bulk API option on the first step of the modules listed below. Learn more about Bulk API.

1. Bulk API

• Applicable to: Delete, Dedupe, Export, Import, Match, Modify, and Verify
• Default setting: no value populated, DemandTools uses Salesforce Bulk API 2.0
  • Batch size can be specified between 1 and 10,000 
• Notes:
  • If a batch size is specified, DemandTools uses Salesforce Bulk API 1.0, which results in slower performance, but offers customization where required
  • If Salesforce Bulk API 1.0 is used, the following limiting behavior can be expected in the generated audit logs:
    • If operation IS successful, new or updated record ID and information is returned
    • If operation IS NOT successful on insert, no record information is returned
    • If operation IS NOT successful on update, record information is returned

2. Use serial mode

• Applicable to: Delete, Dedupe, Export, Import, Match, Modify, and Verify
• Default setting: unchecked
• Notes:
  • Serial mode processes batches one at a time, instead of in parallel
  • This may significantly increase processing time, but can avoid issues such as lock contention