Welcome to Community Week 2025! Join us to learn, connect, and be recognized as we celebrate the spirit of Community and the power of AI. Get the details  

Difference between Backout and Ignore of the update sets

Bhargavi K
Kilo Contributor

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.

1 ACCEPTED SOLUTION

Community Alums
Not applicable

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

View solution in original post

9 REPLIES 9

Musab Rasheed
Tera Sage

Hello,

Yes you are right, just to put in simple words

1) Backout - Once you commit update set and you found you don't need changes which were committed as part of update then then you can use 'Backout' button clicking which will remove all changes which were applied.

2) Ignore - Generally we use 'Ignore' option in update set when we don't want updates which got captured in update set to not to move forward in that case we move it to ignore state.

But in case you have committed update set and later on you move to to ignore state then changes committed will not be removed, and Generally this is being done in Dev instance and not in test instance and Generally it is not done for committed update sets and not even sure if you can do it for committed update sets.

Please hit like and mark my response as correct if that helps

Regards

Please hit like and mark my response as correct if that helps
Regards,
Musab

Got it,, Thank you Rasheed:)

No problem, Feel free to tag me in case you have any doubt 🙂

Please hit like and mark my response as correct if that helps
Regards,
Musab

Ok Rasheed