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 shown in the grid results
- Can be used to "partially" restore a bad merge
- NonMasterOwnerChange File
- 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
Merge Record File
After a merge is complete a Merge Report is created and saved in the DemandToolsMSDData\Logfiles folder. This file tracks the time of the merge, the object type merged, the record ID's, 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 DemandToolsMSDData\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.
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.
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.
