What to do with skipped records after upgrade to new ServiceNow version

[ceraulo]

Hello!

I am managing our client's upgrade to San Diego. I have created update sets for the skipped records. Should I commit these update sets AFTER the upgrade in our production instance?

Thank you.

[Jimmy Akinyemi]

Hi Ceraulo, 

You have done the right thing by capturing the fixes in update set. Best practice is to commit these update sets AFTER the upgrade in our production instance.

Please let me know if this helps.

Thank you.

Jimmy

[Tyson3]

Hi I also have the same question on best practice to follow here.   We have used update sets to track our skip file decisions in our sub environment (merge, revert, etc).  But what I have found is that if we revert a file to "base", it will be tracked to that the update set we created instead of the base version.  Therefore, when we do patches or the next upgrade it will look like it's customized even though we reverted to base. Am I missing something here?

See below for example.  After I moved and update set from our dev instance to our test instance, you can see it's now tracked to my custom update set instead of the base version which should be "System Upgrades: glide-utah-12-21........."

Are we not supposed to use update sets and do this manually in each instance?

[Ankur Bawiskar]

@ceraulo 

It would be nice if you mark your older questions by marking appropriate response as correct so that it helps future members.

Members have taken their time and efforts in sharing the solution/approach.

Regards
Ankur