Run History enables you to review scenarios you have previously run and, in limited cases, undo the final action (such as a merge) on the target database. Both saved and unsaved scenarios are included.
Accessing Your Run History
To access your run history for these modules, select Run History from the top of the Scenarios table on your Dashboard.
Run Time: The time reflected is local to your machine, which may or may not be the machine that ran the scenario.
Scenario Name: Named scenarios have been previously saved. These may be scheduled jobs or unscheduled scenarios run manually. A scenario named "Unsaved [Module] scenario" is a single run that was not saved, so its configuration and properties are unknown.
Module: All modules are included in Run History.
Run By: Run History shows all scenarios in your org, whether run by you or someone else. You can only undo actions for scenarios you have run.
Records Found: The number of records identified by the scenario. If the checkboxes for all records remained checked, all records were included in the final action, and the number will be identical to Records Actioned. Available for Dedupe, Delete, Import, and Modify.
Records Actioned: The number of records included in the final action (such as a merge into your target database).Available for Dedupe, Delete, Import, and Modify.
Undo: If an action can be undone for a scenario, the Undo [Action] button will appear here. Available for Dedupe and Modify.
Audit Log: For all jobs you run on your computer, this column will show a CSV file icon and link to the log file for that specific Run instance. Jobs run on a different computer or under a different login will not link to the audit log.
Scheduled: If the scenario run was a scheduled job, a clock icon will appear in this column. This applies to scenarios run in DemandTools 5.31.0 or later versions.
Defining a Run
What is considered a run in Run History? DemandTools logs a Run every time the scenario reaches the Preview Grid, whether or not an action is performed. This way, you have insights into Runs even when they have no actionable results (0 Records Found), or when an action was possible but not performed (X Records Found, 0 Records Actioned).
Undoing an Action
Before you can undo the final action in a previously run scenario:
- The scenario must have been run within the last 15 days.
- The records must still exist in your Recycle Bin in Salesforce.
- You can only undo actions you originally ran (your login), on the computer where you originally ran them.
- If you added a prefix to any losing, or duplicate, records, you must delete that prefix from all records before attempting to undo a merge.
If you see the Undo [Action] button and haven't emptied your Recycle Bin, you should be able to undo your action.
If the initial merge was run by another user, run by you but on a different computer, or run more than 15 days ago, no Undo [Action] button will appear.
Undoing an action restores that record to its previous state, with the following exceptions:
- Changes made by the Touch records Modify action, specifically altering the last modified date, cannot be reverted.
The Account Contact Relationship (ACR) object is not included in Undo Merge actions. Contacts moved during the merge process won't be moved back as direct relationships, but will stay as indirect. This only affects accounts with ACR turned on.
- For example, if you merge Account A and Account B, and Account B is the winner, any direct contacts from Account A will be moved over to Account B. Their relationship will show that Account B is direct and Account A is indirect.
- If you then try to Undo Merge on that action, these relationships will stay as they are now and no contacts will move back to Account A.
Note: Undoing an action also erases subsequent edits. If you ran a scenario on a record, merged it into your target database, and then made edits to the record afterward, and you undo that merge, your edits will also be undone.