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.
List layout changes cannot be moved through update set. - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • List layout changes cannot be moved through update set.
KB0695265

List layout changes cannot be moved through update set.


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

Issue

Symptoms


After committing of Update Set containing list layout changes, List Layout are not applied in the target instance.

 

Release


All

Environment


All

Cause


Duplicate records in the [sys_ui_list] table for the combination of following fields:

Table, View, Domain, Element, Relationship, Parent, Scope.

When committing an Update Set, the platform does not expect to have these multiple records for the same values and ends up corrupting records. List Layouts have a different coalesce strategy than the Sys ID. 

Resolution


Clean the [sys_ui_list] table by removing the duplicate records and the ones with no Element.

Additional Information


https://docs.servicenow.com/csh?topicname=c_ApplicationTools.html&version=latest 

When committing an Update Set with a new List Layout, the platform is supposed to first delete the current record (if there is one) with the same values for the fields listed above and then insert a record with the data from the Update Set. 

Example Extract from application log, which shows error in coalescing during update set commit

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2018-07-11 15:54:34 (094) worker.2 worker.2 txid=bf7b60b8dbd7 Loading update 7 of 7 from database: sys_ui_list_sysapproval_approver_null with update date 07-11-2018 15:54:33
2018-07-11 15:54:34 (215) worker.2 worker.2 txid=bf7b60b8dbd7 WARNING *** WARNING *** com.glide.script.GlideElementXMLSerializer: Attempted to resolve an invalid reference via a coalesce strategy
on table sys_ui_list for field list_id but retrieved 3 records when querying against said strategy when 1 was expected. Thus the invalid reference could not be resolved.
Please verify the key fields for the coalesce strategy on table sys_ui_list represents the unique key for that table.

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.