After Upgrade to UTAH, I see many P5 skipped records and need help to determine what to do?

[Chandler2]

Questions: 

1. There are many records which has disposition as Skipped Error, for these there is not option to resolve conflict or revert to base option. Only update and delete is there, what to do with these?

2. There are many records which has disposition as Skipped. Most of these sems to be form layout, ui section etc. When doing resolve conflict, I see the changes highlighted but there is only one option, which is revert to base, why so?

What would happen if I do revert to base for these? Will I loose the changes on form?

Please suggest, thankyou!

[Community Alums]

Hi @Chandler2 ,

There can be several reasons for why you get records marked with 'Skipped Error', like for example a system property exists and is only editable by maint or uneditable. Unfortunately the name is a bit confusing as usually 'Skipped' records in upgrade are the ones that have been customized by customers.

These "skipped error" records in the upgrade history usually contains sys_properties data, that may already have been set in your instance. You can review the conflicting data to confirm the values and if the values are the same, you can leave the record as skipped. Most of these skipped error records also has a Priority of 5(low).

when you do a check on the skipped error records your will see that mostly the reason why this was the disposition of these updates is that it belong to a Scoped App Author or the Scoped App Client applications. Take note that these sys_properties are existing in your instance already.

Opening the Show Related Record link for these records results to the message below and no option to edit the record at all:

"This record is in the Scoped App Author application, but Global is the current application. To edit this record click here."

In comparison, open a record with Disposition "skipped" and you will have the options to Resolve Conflicts(comparison of Base system vs. Custom)or Revert to Base System.

Lastly, based on the Priority grade of these skipped error records should not have any effects on the behavior and functionality of your instance.

Also, refer to the thread : https://www.servicenow.com/community/developer-forum/skip-records-there-are-no-differences-found/m-p...

[Matt102 · Accepted solution]

Hi,

1. This SN KB article may be of assistance (official SN stance):

KB0786212

2. Why so?:

There is the option to revert to base, however, by doing nothing, you also have the (implicit) 'option' to retain your configuration/customizations. Also if you use the Resolve Conflicts page you can also merge base and custom versions.

...loose changes on form?:

If you revert to base, yes, you will lose your changes

I have found that to avoid seeing these list/form/section skips it helps to amend forms and lists in a new view, not one of the OOB views

This SN PDF may assist: What’s the process to review and address skipped changes? 

r,matt