Wrong\Incorrect column order\layout in the list reportIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms For specific users, A list report can show wrong/incorrect order of the columns in the list report but not in the actual list. (i.e) It can show different columns in the report than the ones specified in the 'selected' slushbucket as in the attached screenshot. Release Jakarta+ Cause Invalid sys_ui_view record. Resolution Check both the sys_id of the report and user for which the column order is shown wrongly. Filter the name field of the sys_ui_view table with those sys_ids like, https://<instance>.service-now.com/sys_ui_view_list.do?sysparm_query=nameLIKE<SYS_ID_OF_REPORT>%5EnameLIKE<SYS_ID_OF_USER> It's just a temporary view and once its deleted, the column of the report should look fine. There is a chance that this can occur while creating new reports too. In that case, You need to delete https://<instance>.service-now.com/sys_ui_view_list.do?sysparm_query=nameLIKE<SYS_ID_OF_USER>%5EnameLIKE<TABLE_ON_WHICH_ YOU_ARE CREATING_REPORT> Additional Information In the above links, replace <SYS_ID_OF_REPORT> with sys_id of the report and <SYS_ID_OF_USER> with sys_id of the user. In some cases, the link can be like, https://<instance>.service-now.com/sys_ui_view_list.do?sysparm_query=nameLIKE<SYS_ID_OF_REPORT>%5EnameLIKE<USER_NAME> where you should replace <USER_NAME> with user name of the user. In that case, the issue could be because of a PRB and KB0656974 could help resolving the same.