When this box is checked, DemandTools calls in Salesforce's merge call to perform the merge. This option is ONLY available when merging Accounts, Contacts and Leads and is the default for all pre-built scenarios and any new scenarios built from scratch.
If this box is unchecked for any reason, or it is not available (e.g. merging objects other than Accounts, Contacts, or Leads, e.g. Opportunities, custom objects etc.), the following caveats will apply. Please review carefully!
Longer Merge Time Per Group
Instead of 1-3 seconds per group merged with "Use Salesforce Merge" checked, each group will take about 7-10 seconds to merge.
Significantly More API Calls Used Per Group Merged
Merging in Single Table Dedupe will use a minimum of 1 API call per group merged when "Use Salesforce Merge" is checked. This calls in Salesforce's API merge call which wraps the majority of the merging process within 1 API call. If this box is unchecked significantly more API calls will be used per group.
Check the sub-objects that should be moved from any non-master records to the master record. If the object allows re-parenting then the lookup field to the object being merged will be updated to that of the master record, otherwise the sub-object will be cloned and re-inserted on the master record.
Note: This option is ONLY available when not using the Salesforce Merge call. When using the Salesforce merge call ALL sub-objects will be moved to the master record.
Objects Owned by Inactive Users
Salesforce does not allow updating certain types of objects owned by inactive owners. To "merge" sub-objects the parent ID needs to be updated to the master record id. In order to ensure that all sub-objects are merged regardless of the status of the owner we provide various "Inactive Ownership Exceptions".
- Reassign to master object owner and then re-parent
- Reassign to current user (the user that is logged into DemandTools), then re-parent
- Keep ownership (requires a spare Salesforce license). The user will be reactivated, update object owner and move object, then deactivate user.
- Tasks and Events that are owned by inactive users will be moved in the deduplication process.
- Starting in Winter '16 a user permission called "Update Records with Inactive Owners" can be enabled making the above options unnecessary. However code changes will need to be made in DemandTools to address this change. For the time being, users will need to continue to select one of the above options to address sub-objects with inactive owners.
Retaining the CreatedDate & CreatedByID for Cloned Sub-Objects
There will be some sub-objects that cannot be reparented, so in order to merge these objects onto the Master record they need to be cloned instead. When this happens the "created" and "last modified" fields become the date of the merge (e.g. the original created information is not retained).
Starting in Winter '16 there is a user permission called "Set Audit Fields upon Record Creation". When this is enabled DemandTools will be able to re-insert the original created/modified information when the sub-object is cloned.
More information on how to enable this permission on Salesforce can be found in this Salesforce help document.
Converted Leads NOT Updated When Merging Accounts/Contacts/Opportunities
When merging Accounts/Contacts using the Salesforce Merge Code, if there is a converted Lead associated with a non-master record, the convertedobjectid's on the converted Lead is updated to the master record's ID (i.e. the convertedcontactid, convertedaccountid).
When "Use Salesforce Merge" is unchecked, this CANNOT be done, as converted Leads cannot be updated via the Salesforce API.
This will affect the accuracy of converted Lead reports since there will no longer be a link from the Account/Contact/Opportunity back to a converted Lead.
Note: It is recommended that "Use Salesforce Merge" ALWAYS be checked when merging Accounts/Contacts.
Duplicate Campaign Exception
Only applies if merging Leads or Contacts and only to DUPLICATE campaign member records (e.g. the same campaign exists on the Master and Non-Master records).
- Use Master: Keep the Campaign Member from the Master Record
- Use Most Recent: Keep the Campaign Member that has been most recently modified on all the records
Cloned Custom Objects
Sub-objects of cloned objects will be re-parented. Ensures that ALL custom objects are merged, not just the directly referenced ones, ones that truly are beneath the custom object in database hierarchy (we expect very, very rare). The recommendation is to always keep this checked.