Default "List Layout" is not working for all users.

vaibhavdesai
Kilo Expert

‎02-16-2016 10:32 PM

Hello,

On Change Request and Incident "List layout", I have added 6 columns as default columns by navigating to "Right click on header of list >> Configure >> List Layout >> Added required column >> Save". Now, according to Servicenow default behaviour when any user click on "Gear icon on list >> reset to column default button". Default column layout should be applied.

Currently, For me some users are there in my instance for whom default layout is completely different than what is set by me.

Strange thing is, for 90% of users it is working perfectly fine. But, For few users it works on Change Request and does not work on incident OR works on Incident and does not work on change request. When they click on "Reset to column default"   they are seeing completely different layout.

Is there any other way from where List Layout can be changed? What could be the possible reason for this behaviour? I have checked all ACL, Client Script running on this tables.

Regards,

Vaibhav

0 Helpfuls
  • 5,658 Views
7 REPLIES 7

Anurag Tripathi
Mega Patron
Mega Patron
In response to vaibhavdesai

‎02-18-2016 01:58 AM

long shot...but try clearing cache on server and client side both.


-Anurag
0 Helpfuls

vaibhavdesai
Kilo Expert
In response to Anurag Tripathi

‎02-18-2016 02:06 AM

Hi anurag,



Tried cache.do. But, still for some users completely different default layout exist. And strange thing is this issue is only on Incident. On "Incident Task", "Change Request", "Change Task" it is working completely fine.



Regards,


Vaibhav


0 Helpfuls

Eric Jensema1
Giga Contributor

‎04-26-2016 08:52 AM

I don't know if you solved this, but I just had the same problem. Here's what I needed to do to fix it:



  1. Navigate to the list view of the "sys_ui_list" table
  2. Filter to the table that you're working with
  3. If there are multiple entries, delete all but the most recent one.


I noticed that originally I had an entry that had both the "table" and "parent" fields pointing to the same table. I don't know if that was the cause, but it was creating a whole lot of entries that would randomly work and then fail. Once I cleared all but the most recent listing for the table that was having problems, it started working as I expected.