Upgrade - Capturing repairs in an update set

jpspurlin · ‎07-13-2017

I have read several of the posts on upgrading and update sets and they don't address my specific question.

We have 3 environments. We have started in our sandbox to upgrade from Geneva to Istanbul. We are trying to get as much as possible back to OOB. So, we are spending a good bit of time reviewing the skips and reverting back to OOB.

Should we be capturing this in an update set?
Can we apply this update set to our second environment (Dev) and not have to repeat this manual skip review process?
If we do apply the update set to our second environment - can we apply it before we do the upgrade?
1. My thought is that if we have reverted many of the items to OOB before we do the upgrade, then we won't see those as skips when we do the upgrade. But I'm not sure we can apply an update set done on an Instanbul instance to an instance that is still on Geneva.
If we have to apply the update set after we do the upgrade, I think I read that it will not update the skip log. Is that correct?

Thanks,

Jan

jpspurlin · ‎07-20-2017

I submitted this question to HI and got a slightly different answer.

Reverting a customization is not tracked in update sets. You must perform this procedure on each instance for which you want to revert your customizations. Additionally, committing update sets across ServiceNow versions is not advised. There can exist schema changes between versions that would cause issues during committing update sets.

Here are some useful articles that will help you to develop a solid plan for your upgrade:

Upgrade Best Practices Reverting Customizations

View solution in original post

Tim Woodruff1 · ‎05-10-2023

@jpspurlin wrote:
Reverting a customization is not tracked in update sets. You must perform this procedure on each instance for which you want to revert your customizations.

....what?
That isn't true, is it?
I've never seen that behavior. Pretty sure reversions are indeed tracked.