Notifications

364 views

Description

The Resolve Conflicts UI action on a skipped record displays a Payload is not found message if there is no sys_update_xml for that record. The system looks for a sys_update_xml with the file name that is in source control, without considering whether that file has coalesced and exists under a different name/sys_id.

Steps to Reproduce

 

  1. Navigate to System UI -> Views module.
  2. Search for Name = default.
  3. Customize that record by changing the title. This should create a sys_update_xml record for this view in the current update set.
  4. Upgrade the instance.
  5. After upgrade, navigate to System Diagnostics > Upgrade History module, open the sys_upgrade_history record for the upgrade. This should be the first record when sorted in descending by created date.
  6. Filter down the skipped list to only sys_ui_view records with Target Name = default.
  7. Click any of these records, excluding the one modified in step 3.
  8. Click Resolve Conflicts.

The user sees a Payload is not found error message.

Workaround

This issue is under review. If you are able to upgrade, check the Fixed In field below to determine the versions that have a permanent fix. You can also subscribe to this known error article (click Subscribe button at the top of the article) to receive notifications when more information is available about this issue.


Related Problem: PRB715145

Seen In

Helsinki Patch 0 Hot Fix 1
Helsinki Patch 2
Helsinki Patch 5
Helsinki Patch 6 Hot Fix 1

Fixed In

Jakarta

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-03-16 06:07:04
Published:2017-08-24