Batch Update Set Errors - not Backout.

[_Samay]

Hi Team -

We have created 10 catalog items and there is one update set for a catalog item where we keep all of their developments 

We would require to push all of those catalog item from DEV to TEST so we created a parent update set and all catalog item updates are tagged under that parent update set also catalog items update sets are having some variable set and their variables those are also getting used into other developers update sets.

But due to some reason, I backout that parent update set, while backing out it’s throwing errors, I have checked those errors and selected Keep Target Version.

But, after that also update set did not back out fully whereas I can many errors, as well as child update sets are still there into UAT.

How we can completely remove all data as well as update set parent and all child.

Thanks,

[Tanushree Maiti]

Hi @_Samay  ,

After waiting some time , if you see it has not properly reverted the changes, 

in that only way to create a update set in Dev-> manually revert the changes in Dev so it got captured in Update set -

>then move to Test.

If all catalog item has no dependency on other (like via variable set), try to create update set per catalog item (where revert was not done fully).

We faced this issue couple of times. that way we fixed it.

[Ankur Bawiskar]

@_Samay 

any reason to backout?

[Dr Atul G- LNG]

Hi @_Samay 

Backout is not easy or straightforward, especially when it involves merges or batch updates. ServiceNow does not always recommend doing a full backout; it’s usually better to send a fix. First, identify what is not working and consider disabling that feature instead of backing out the entire change. A backout can sometimes introduce more issues than leaving it as is and sending a proper fix.”