Slow List View When Displaying All Available ColumnsIssue When a List View is customised to display all available columns, users might see impacted performance and slow load times or even transaction timeoutsCauseFor every field displayed within a list view the platform needs to 'normalise' the data to presented to users. This might be as simple as looking up the name of a referenced user, formatting a date or selecting the correct language for a choice field. However some are more involved such as determining the stage of a workflow and presenting graphics accordingly. Simply put, the more data you try to display within a list view at the same time, the longer the transaction will take to process the results. Combine this with the number of rows that are displayed and the ACL that need to be processed to confirm that user are allowed to view certain records and users can quickly see increased response times. For tables such as 'incident' or 'cmdb_ci' which have a large number of fields the result of adding all of them into a list view will be very impactful to performance and transaction response.ResolutionServiceNow recommends that list views are only configured with the essential data required to review records. It is also highly recommended that you keep the default row count of 20 records to minimise performance impact from ACL processing. If you do accidentally add these columns into a list view and you cannot load the list to change the configuration then you can always load the list view with the filter only and no records, which will then allow you to access the column configuration. This can be done via adding '&sysparm_filter_only' to the URL. The following URL is an example on how to load the 'incident' list with only the filter options displayed: https://<my-instance>.service-now.com/nav_to.do?uri=incident_list.do&sysparm_filter_only