Difference between Backout and Ignore of the update sets

[Bhargavi K]

Hi all,

Can you please brief me the difference between the Backout and Ignore of an Updateset. For suppose if we make the update set as ignore which is moved from dev to test which is already committed and then it is changed to ignore, is all customizations are still there in the particular form, if we backout the updateset the all customizations are romoved. Please tell me the difference.

[Musab Rasheed]

You are marking others answer as correct, Since I replied first and In case you feel my answer was sufficient to understand the difference then mark my answer as correct, otherwise ignore it.

[Community Alums · Accepted solution]

Hi @Bhargavi K ,

Here is the scenario when we use backout of update set:

- We develop code in DEV using our update set.

- Then we promote the update set to TEST. If we see something is broken and become hard stop in TEST, we backout the code in Test. We never backout the code in Dev.

- If the backout is successful without error then the code that we moved to Test will be totally removed and reset to the previous state.

Here is the link for more details: Back out an update set

You should always set Completed update sets on the production instance to Ignore. This state will also ensure that the update set is not committed again when cloning the instance.

It's a great idea to set your prod update sets to Ignore as a matter of your process. Now when clone back to Dev, they aren't in your way for future updates.

Learn more from this Article : Why you should set your completed update sets to 'Ignore' on production

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Bhargavi K]

Thank you Sandeep

[Aman Kumar S]

Hi @Bhargavi K 

Backing out an update set creates delete updates in the current update set. If you commit, back out, and then reapply a remote update set, errors appear in the previewer because the deleted updates are considered more recent changes and cause collisions.

Warning: Do not back out the Default update set. This action can damage the configuration of the instance.

The back out process reverses both record-level updates and changes to the dictionary. Some changes caused by a back-out can result in data loss. These are the expected results of the back-out process:

An ignored local change always points to the current version for the record. You cannot push ignored records to another instance.

Feel free to mark correct, if your issue has been resolved, so it ends up in solved queue.

Will be helpful for others looking for the similar query.

[Bhargavi K]

Thank you Aman