DOING BACKOUT OF AN UPDATE SET DELETES THE ENTIRE UPDATE SET?

[vksnow]

I have created an update set with some customizations and loaded them into other instance too.

After sometime i deleted a customization by selecting a customization it in the update set (under customer update sets), then by clicking on backout, the entire update set got deleted and i lost

the customizations too which i have done in the instance.

Is it right way of working backout in update sets?

[Arindam Ghosh]

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

Hope this helps you.

Thanks,

Arindam

[Harsh Vardhan]

Hi Venkat,

if you backout your update set then all the customization that you had captured in that update set will out and customization will no longer available on your instance.

but if you check in your lower environment that will be available . you can again retrieve that update set from lower to production environment .

eg: you have migrated the changes from Development Environment to Production Environment. then you had backout then all the changes had made on prod will not longer available . but if you want it again then you need to retrieve it from dev to prod in a same way that you made .

Using Update Sets - ServiceNow Wiki    

[Jaspal Singh]

Hi Venkat,

Yes, this is how backout process works. Once committed update set is backed out all its updates would be rolled back. If you want some updates to stay all you need is to go back to your environment where update set was created look for customisations in sys_update_xml table get it removed & then again get it imported in the your environment where it is required to be committed.

If you think that selecting some updates & getting in it deleted once committed & then backing out would involved removal of only those updates then it won't. Back out would mean removal of everything regardless of selection made.