How to handle "skipped records" as part of ServiceNow Upgrade?

Suggy · ‎02-26-2022

We have 3 instances. DEV, TEST and PROD.

Lets say I have cloned PROD over DEV, then upgraded DEV instance, reviewed all the skipped records (assume I have 100 skipped records) in DEV and have captured required changes in Update set.

Now when upgrade TEST instance, I dont want to review all those 100 skipped records as I have already reviewed in DEV instance.

How should I handle this? If I move my update set to TEST after upgrading TEST instance, will there be any changes to my skipped records? or what exactly will happen to my skipped records after I move my update sets?

Craig Gruwell · ‎02-27-2022

Hi Suggy,

After you commit the update set in TEST, when you navigate to the Upgrade History you should expect to see the 100 skipped records appear on the "Skipped Changes Reviewed" related list (as if you performed the same remediation steps in TEST that you did in DEV).

View solution in original post

Dominik von Fi1 · ‎02-28-2022

Hi All,

I fear this is not true from what I experienced in the last couple of upgrades we did. When you move the update set, the skipped record entries are not modified as they do not have the same sys_id on each instance. The update set just moves the changes to the actual records but not the skipped record entries.

However, I just always move the update set and ignore the skipped change record entries on the PROD and TEST instance 🙂

Jon Epstein · ‎02-28-2022

I concur with this. It is a "less than ideal" solution. You have to just "TRUST" that the decisions captured in the update set are processed properly in TEST and PROD, but without digging into every. single. record., you cannot visualize it.