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

wengkin · ‎01-03-2018

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.

Lakshmaiah Dump · ‎01-03-2018

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

View solution in original post

sachin_namjoshi · ‎01-03-2018

Hi,

Backing out update set is NOT best practice since you may face lot of issues in future.

In your case, You should create new update set in your source instance to capture required customer updates and then move this new update set to target instance.

Regards,

Sachin

wengkin · ‎01-03-2018

Hi Sachin,

I am a beginner at this. I only realised that it was not a good practice after reading more online to find a solution. I had originally wanted to "redo" the update set with the thought that it should rerun the same script to insert/update the records from the update sets. Will this ever be possible?

My intention was to create an update set for a new catalog item that was created in my dev. If I had to redo the same update set, will I not have to redo all the steps of creating the same catalog item on the same dev?