Upon completion of the merge various CSV files will be written out for tracking purposes.
Merge Record File
Basic report of the groups that were merged. After a merge is complete a Merge Report is created and saved in the DemandToolsData\Logfiles folder. This file tracks the time of the merge, the object type merged, the record ID's, Owner ID's and any selected extra field for logging for the master and all the non-master records.
A separate file will be created for each merge pass. The naming convention for the file is MergeRecord_YYYYMMDD_X.csv. The "X" will be a number starting with 1 and will increment with each dedupe pass done that same day.
Dedupe Merge Data File
After a merge is complete a file containing all field data from all records in the results grid is saved in the DemandToolsData\Restore folder. In the event of a "bad" merge, this file can be used to restore the field data to their values prior to the merge.
- A before image of ALL fields from all the records shown in the grid results
- Can be used to "partially" restore a bad merge
This file can be used to restore field data ONLY. THERE ARE NO FILES THAT TRACK WHICH SUB-OBJECTS WERE MOVED IN A MERGE. It is still highly recommended that a full backup of the database be taken before performing a large scale deduplication, and that Salesforce history tracking also be used to track changes to any key fields that could be updated during a merge via "Update Fields Where Master Empty" or "Combine Field Values". Tracking changes to parent ID fields for any sub-objects that could be moved during the merge (e.g. Account ID changes to the Contact and Opportunity tables) can help determine which sub-objects where moved during a merge aiding in the manual process to move sub-objects back to their original parent if needed.
A separate file will be created for each merge pass. The naming convention for the file is {Objectname}DedupeMergeData_YYYYMMDD_X.csv. The "X" will be a number starting with 1 and will increment with each dedupe pass done that same day.
Non Master Owner Change File
If records are merged with different owners, a non master owner change file is saved in the DemandToolsData\Logfiles folder when the merge is complete. This file captures the owner ID’s for any non-master records where the owner was not the same as the master owner.
- Captures the owner ID’s for any non-master records where the owner was not the same as the master owner
- This file can be used with a post process to add the non-master owner to the Account Team of the master record
- ONLY created for merge groups with different owners
The primary purpose for the creation of this file is to add the non-master owners to the Account Team for the master record. This can be done using this file as the input source to the MassEffect module to insert into the AccountTeamMember table. Complete instructions for this process can be found in the following Validity Community Forum: Adding a Non-Master Owner as a Team Member/Share on the Master Record When Merging Records in Single Table Dedupe.
This file is appended throughout the course of a particular day, so ALL merges for that day are tracked in this one file. The naming convention for the file is NonMasterOwnerChange_YYYYMonthDD.
Sub Object Owner Change File
If the Reassign to Master Owner option is selected for specific sub-objects, a sub object owner change file is saved in the DemandToolsData\Logfiles folder when the merge is complete. This file captures the record ID's for any sub-objects that had their ownership changed along with the previous owner ID's. The Master Record ID and Owner ID's are also captured for reference. This file can be used to restore the original ownership if needed.
- Tracks any sub-objects that had their ownership changed to match the master owner via the Reassign to Master Owner option
- Can be used to revert back to the original sub-object owner if needed
A separate file will be created for each merge pass. The naming convention for the file is SubObjectOwnerChange_YYYYMMDD_X.csv. The "X" will be a number starting with 1 and will increment with each dedupe pass done that same day.
Note: Applies to merging Accounts, Contacts and Leads only when the "Use Salesforce Merge" is checked. Does NOT APPLY when merging custom objects or un-checking this option.
This file ONLY contains the sub-objects that had their ownership updated during the merge. It DOES NOT contains all sub-objects moved in the merge nor does it contain the original parent record ID's. Therefore it cannot be used to used to restore sub-objects to their original parent records (the merged records).
