Upgrade Skipped Records without Resolution

[Felipe Barbosa]

Hello all,

As we prepare to upgrade our instances to Vancouver we have made the exercise of upgrading a copy of our production to better understand the impact of the upgrade and also to have the details of the Skipper Records we would need to review.

I noticed that on the Upgrade Details form, we have the Related Lists for "Skipped changes to review", but I noticed that in this list we have only the skipped records with disposition as "Skipped" that has a resolution value, most likely it's "Not Reviewed" as these are still pending, however, there is a big chunk of records with disposition as "Skipped" but Resolution is Empty.

My question is, what do we do with these? What is your approach in your current upgrade process?

Thank you in advance!

Best regards,

Felipe

[Adam Obuchowsk1]

I second the question. Recently I noticed, that after a patch in my case.

A given file may be reported in one environment as:

Disposition=Skipped; Resolution=Not Reviewed

And the same file in another environment reported as:

Disposition=Skipped; Resolution=<empty>

Which is confusing, as it's marked for review in one place, and not the other. I.e. DEV Skipped Items to review: 12 (count) I.e. UAT Skipped Items to review: 6 (count) (the other 6, still skipped, but empty resultion causes them not to be counted)

[matt_kean]

I wondered the same thing. ServiceNow appears to filter to records where 'Changed' = true.  I got my numbers to match by filtering like -

upgrade_history=xxx,

disposition=skipped,

changed=true,

resolution_status=not_reviewed