Plauti Restore can undo all record changes that are available for restoring.
- If a record insert or field update is present in the Restore Changes overview, it can be undone.
- If a merge or deletion is present in the Restore Changes overview, and the loser record or deleted record is still in the Salesforce Recycle Bin, it can be undone.
Old record changes might be removed and cannot be restored anymore. In the Restore Settings you can set how long and how many changes should be kept.
Restoring Merges
When undoing Merges, relationships are restored as well, but within limits (see below).
Undo Merge is available for both Plauti Deduplicate merges and Salesforce merges. Because of Salesforce limitations, it's only available for Accounts, Person Accounts, Contacts, Leads, and Cases.
A Restore Changes overview with different Change types. Each line is a change that can be undone with the Restore button at right.
Prerequisites
- You have enabled Object Tracking for the Object where you want to undo a change.
- For field updates you have specified fields to track.
- For merges you have specified related Objects to track.
- The change you want to undo was made after tracking was set.
- You have added the Plauti Restore component to record pages. (optional)
Accessing the Restore Changes overview
- Open the Plauti Restore app > tab Restore Changes.
- This overview displays all tracked changes, of all records of all tracked Objects.
- Merges can only be undone via this overview.
- Open the record where you want to undo a change. The overview with tracked changes is displayed in the Plauti Restore component on the record, if enabled. If the component was placed on a separate tab, the tab might have a different name.
- This overview only shows tracked changes of that specific record.
- Merges cannot be undone via this overview.
- Via this overview you can only undo one change at a time.
Restoring an Insert, Field Update, or Deletion
- In the changes overview, find one or more changes you want to undo.
- At the right of a change, click Restore
.
Or, if you selected multiple changes, click Restore Selected
at the top of the list to restore them all in one go. - In the pop-up, confirm that you want to restore the change.
The restore has been applied. In the Changes overview, the restore will appear as a new change, that you can then also restore ("re-do" as it were) if the restore was done accidentally.
Restored Inserts are listed as a Deletion, and restored Field Updates as another Field Update. Restored Deletions are not displayed in the Changes overview.
Restoring a Merge
Merges can only be undone once the merge process has fully finished.
Furthermore, when undoing a merge, relationships will be restored as well, but within limits (see below).
- In the Plauti Restore app, on tab 'Restore Changes', find the Merge you want to undo.
- At the right of the Merge, click Restore
. Or, if you selected multiple Merge changes, click Restore Selected
at the top of the list to restore them all in one go. - In the pop-up, confirm that you want to restore the merge.
The merge is undone and you are returned to the Changes overview.
Both the Master and loser record have now been returned to their previous state.
Note that the changes that restored (undid) the Merges are not displayed in the Changes overview.
Not all related records restored
Not all related records can be restored when undoing a merge, either because of the type of Object, or because of Salesforce limitations (record and query processing limits).
- Generally speaking, Plauti Restore can restore related records of the following Objects when restoring a merge:
Standard Salesforce objects (Contacts, Opportunities, Cases, Tasks, etc.)
Custom objects with lookup or hierarchy relationships
Objects that are queryable and updateable
Objects whose relationships can be reparented
- Related records that cannot be restored to their original record are for example:
Share objects (e.g. AccountShare, ContactShare)
History objects (e.g. AccountHistory)
Tag objects (e.g. AccountTag)
Feed items, comments, and other Chatter items
System objects that cannot be reparented
Attachment-related objects
These types of objects cannot be selected for Related Object Tracking in the Object Configuration.
- Sometimes a large number of related records needs to be restored, for example because the merged records contained many related records in total, or related records from many different Objects. In these situations the process to restore the related records can exceed the DML Statements limit or Salesforce Governor Limit.
- When the DML Statements limit (total number of related records) is reached, the restore action cannot be processed at all and will fail. Usually this occurs at around 100 related records or more.
- In case of the Salesforce Governor Limit (total number of queries, for example because of related records from many different Objects), only a part of the related records can be restored. To make sure that at least the most important related records are recovered when undoing such a merge, sort your tracked related Objects in order of priority, with the most important objects listed first.
Record not present in Recycle Bin
If you see a message stating that a record cannot be restored because it is not present in the Recycle Bin, this means one of two things:
- You clicked 'Restore' at a Merge or Deletion that was already restored earlier.
Or - The record cannot be restored because it was already permanently removed from the Salesforce Recycle Bin, and only the merge or deletion metadata is still present in the Restore Changes overview. Read more in Plauti Restore and the Salesforce Recycle Bin.
