Unable to redo the same update set after i back out from the first commit

[wengkin]

I have committed an update set, backed it out, and wanted to redo the same update set again. However when I run the preview it tells me "Found a local update that is newer than this one". How can i commit the same update set without facing this problem? I was testing how to do a proper update set from my personal developer instance to a test instance. But now regretted doing the back out as I cannot re-commit the first committed version.

[Jaspal Singh]

Hi Weng,

You can choose option compare update set when you re-commit update set. Look for the differences & then accept or skip it accordingly. Once done you will then have option to commit it again.

This error possibly comes when the update set contains changes that are already in place in the instance being committed along with additional updates.

[wengkin]

I actually deleted the first update set from the local instance. (Although i read later that this was not a recommended approach).

Where can I find the compare update set option?

[Lakshmaiah Dump · Accepted solution]

Hi Weng Kin Chon,

1. Once we back out we can't redo the back changes.

2. You want to commit your changes use the option "Accept remote update".

For your reference : https://docs.servicenow.com/bundle/istanbul-application-development/page/build/system-update-sets/ta...

Hit Like/Helpful as when felt

@Lakshmaiah

[wengkin]

I had 130+ updates that i had to manually "Accept remote update". It kind of worked as it recreated the service catalog item i had original prepared in the update set. Although I noticed some "errors", for example, my service catalog item started having 2 same service catalog selected.