skipped upgrade items show no difference when attempting to resolve

TT21
Tera Contributor

‎09-20-2022 06:51 PM

Have just completed the upgrade of non prod instance from Rome Patch 9b to Tokyo.
Running the Upgrade Preview showed 59 records predicted to be skipped and reviewing these they contained customisations. After running the upgrade there were 411 skipped records to review. 380 of these are sys_security_acl settings and when attempting to resolve conflicts the screen show message "There are no differences found". A check of the upgrade log shows an entry like "Skipping because of database override: update/sys_security_acl_ffed35d2c72010100a9b5d83c7c26046.xml" for each one. Reviewing the differences shows the base has the sys_id for the Operation and the Customized has the friendly name - no other differences could be seen.
Is their anything I can do to stop it generating these skipped records and\or avoiding having to address each one ?

0 Helpfuls
  • 2,879 Views
12 REPLIES 12

Philippe Casidy
Tera Guru

‎12-14-2022 05:13 PM

FYI, I am currently experimenting an upgrade where I set "Replace on Upgrade" to true all those following records:

/sys_update_xml_list.do?sysparm_query=sys_updated_by%3Dsystem%40snc.maint%2Cadmin&sysparm_view=

 

They correspond to the Report_view ACL activation.

 

I understand they are customizations in San Diego (and probably before) and OOTB in Tokyo, that's why I am trying to set them to be replaced on upgrade only before upgrading to Tokyo.

 

0 Helpfuls

Mary S
Mega Sage

‎12-22-2022 11:15 AM

I'm seeing the same after our upgrade to Tokyo in our dev instance.  What did you end up doing @TT21 ?

PRB1579250 isn't showing up on the support site.

0 Helpfuls

TT21
Tera Contributor

‎12-22-2022 02:44 PM

I set them all to reviewed. In the response from ServiceNow they said: "

We are tentatively expecting the fix for this PRB1579250 in the upcoming Tokyo Release/Patch.

For the time being, I believe you can ignore these skipped records."

Also suggested an article

"Please also review the article KB1121670 for additional details about what you need to do before/after an upgrade (patch, family, or store app):

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1121670"