97 views

Symptoms


Users are seeing that their list layout configuration has changed unexpectedly. Columns the user does not want to see are now displayed or fields the user added to their list layout have disappeared.

Release


This can occur in all releases

Cause


There are multiple list layout records for the Incident table in the Default view where the User field is empty. Having multiple system default records can cause the platform to get confused on which is the actual Default list view to use and could randomly reset a user's personalized list as a result.

Resolution


Usually, a list layout record will have a user name associated to it, identifying that for a specific view, this is the personalized column configuration on a table for this individual user. There can be several list layout records for the same table with different user names, as each user has the ability to personalize the columns that are displayed as they see fit.

When a list layout record has the user field empty, it means that this is the system record to be used for the specified view by all users. Each individual view can have a system default layout record for every table.

There should only be one "user is empty" list layout record for each table per view, as this is the default configuration for all users unless they personalize the list on their own. You can check if your system has multiple records by navigating to the following URL for your List (sys_ui_list) table-
https://<INSTANCE_NAME>.service-now.com/sys_ui_list_list.do?sysparm_query=name%3Dincident%5Eview.titleSTARTSWITHdefault%5Esys_user%3D%5EparentISEMPTY&sysparm_list_mode=grid
 
If there are multiple records on this list, please look through them and identify the one layout you would like to keep for your system. Then delete all the extra items. Deleting these excess records will not impact your users.

Additional Information


If a customer is on an early Geneva patch, they might experience their list layouts reverting to those of users who have the same roles. This is a separate issue and has been documented in Known Error KB0584506 (https://hi.service-now.com/kb_view.do?sysparm_article=KB0584506).

Article Information

Last Updated:2018-04-16 09:10:45
Published:2018-04-11