sys_ui_section skipped records on upgrade

[snoozer]

We just upgraded our ServiceNow version and I'm looking through skipped records. There are a lot of skipped records related to the sys_ui_section table. Not unexpected. I'd really like to see which forms these apply to, but I can not figure out how to find them. Usually there is a "show related record" link so I can go to the actual record, but there is no such link on these records.

When I try going directly to the UI Section record URL with the sys ID specified, I get a "record not found" message.

How can I find out which forms these skippeed records allude to? I've just been opting to retain our customizations because I want to keep whatever our users are used to, I would really like to know what it is I'm retaining and what are the actual changes ServiceNow made.

[Sandeep Rajput]

@snoozer Did you try to search with the just the sys_id in sys_ui_section table. Ideally, the record should be present in it.

Also, during upgrade, skipped changes related to form layout should ideally be retained as layouts are generally configured based on an organisation/users' need and they will differ from the OOTB layout in most of the cases.

[snoozer]

Yes I did. No records are returned.

I do plan on retaining our own changes. I just would like to understand what I'm looking at.

[Mark Roethof]

Hi there,

You should be able to find them, or worst case look in the XML for the table name. If its really record not found, that usually indicates being deleted / not present on the instance / etc..

With Xanadu, there are new Skipped Record Rules introduced, amongst them to... ignore sys_ui_section records which should lower the amount of Skipped Records a lot. I'm not a fan of ignoring sys_ui_section records though so I wouldn't advice this, but just informing you.

[snoozer]

Thanks. Where in the XML would I look for it? Is it the "table" attribute in the very first XML element?

If the record has been deleted, do you think the best action would be to "revert to base?" Not sure why any of my team would be deleting records like this, but I guess it's a possibility.