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,

[Dr Atul G- LNG]

Hi @_Samay 

Technically, you messed up another instance earlier. backout is causing errors. In my opinion, a better approach is to move the update to a Test environment, test the functionality, and identify what’s not working. Then build the fix in Dev first. Remember, you’re still in Test, not Prod, so there’s time to correct issues without affecting production. Don’t worry—mistakes happen, and we all learn from them

[Mark Manders]

On straightforward things, you can backout, but not when it includes a lot of catalog items and their variables/variable sets and especially when it's batched. You messed up your TEST instance.

The only way to get this correct is to import the batch again and just accept everything (or better yet: create a new batch with only the things that are correct and move those). 

If something goes wrong with an update set, just fix on DEV and move again. Backing out will have consequences you can't oversee.