Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Personalizing a list layout can create the sys_ui_list record in the wrong scope resulting in skipped components during instance upgrade - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Personalizing a list layout can create the sys_ui_list record in the wrong scope resulting in skipped components during instance upgrade
KB0752476

Personalizing a list layout can create the sys_ui_list record in the wrong scope resulting in skipped components during instance upgrade


2834 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

When personalizing a list layout, it will generate the sys_ui_list record in whatever the current session active scope is. This results in two or more sys_ui_list records matching the coalesce strategy, but having different scopes, which will generate a Skipped Error during upgrade.

Steps to Reproduce

1) Make sure you are in the Global scope.
2) Go to cab_agenda_item (or any non-globally-scoped table).
3) Personalize the list layout.

Observe the generated sys_ui_list record is in the Global scope instead of the table specific scope.

Workaround

Pre-early-London list personalization used to incorrectly generate sys_update_name records. This issue does not occur in currently supported versions.
If an instance was upgraded and still shows this problem, the cause is old data still present in the sys_update_xml table for personalized lists. Cleaning it up will resolve the issue.


Related Problem: PRB1314254

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.