69 views

Description

The 'Revert to Base System' UI Action on the 'Upgrade Details' and 'Resolve Conflict' forms for 'Skipped' records does not work. The issue occurs when an upgrade skips loading a version and that version does not have a [sys_update_version] record with a State of 'Current'.

NOTE: If you are seeing a 'Payload not found' error when clicking resolve conflicts, please refer instead to PRB1249568/KB0635467.

 

Steps to Reproduce

The issue occurs when an upgrade skips loading a version and that version does not have a [sys_update_version] record with a State of 'Current'.


To steps below should simulate the same scenario:
1) Identify and modify a record included with a plugin, like a Script Include record.
2) Upgrade the plugin.
3) Delete the 'Current' record in the [sys_update_version] table.
4) Click on the 'Revert to Base System' UI Action by drilling into the [sys_upgrade_history_log] record or selecting it from the right click menu on the list view.

Notice nothing happens and the record stays in the 'Skipped' State, instead of being reverted to the base version.

Workaround

There is no known workaround for objects which have a different Sys ID than the OOB object, basically objects with a different coalesce strategy than the Sys ID.


For non-deleted OOB objects which coalesce on the Sys ID: make a trivial modification to the target record (like modify the description). This generates a [sys_update_version] record with the state of 'Current'. Reverting to base system after that should work.


For Deleted OOB objects which coalesce on the Sys ID: restore the deleted object using the [sys_metadata_delete] table and the 'Restore File' UI Action provided that you still have a record for that object in the [sys_metadata_delete] table. This generates a [sys_update_version] record with the state of 'Current'. Reverting to base system after that should work.

 


Related Problem: PRB1235020

Seen In

There is no data to report.

Intended Fix Version

London

Fixed In

Jakarta Patch 7
Kingston Patch 1

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-05-14 09:22:19
Published:2018-02-25