Improve Workspace List Performance by Disabling Record Count Badges - Support and Troubleshooting

Improve Workspace List Performance by Disabling Record Count Badges Summary .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Workspace list views slow down due to expensive count queries. On tables like sys_audit , cmdb_rel_ci , and cmdb , calculating total records can be more resource-intensive than fetching the list data itself.

Solution Enable glide.ui.list.seismic.omit.count to skip count badge calculations.

Alternatively, use glide.ui.fetch.list.record.count.asynchronously to defer counting until after list data loads (if counts are still needed).

How to Configure Step 1: Navigate to System Properties Type sys_properties.list in the filter navigator and press Enter Search for glide.ui.list.seismic.omit.count Click New if it doesn't exist Step 2: Choose Your Configuration Instance-Wide (all tables):

Type: True/False Value: true Table-Specific (comma-separated):

Type: String Value: sys_audit,cmdb_rel_ci,change_request Step 3: Test Save the property, clear browser cache, and verify the count badge is gone.

When to Use Use this property when:

Users do not rely on exact record counts Count query latency noticeably delays list rendering Pagination/search is sufficient for navigation Do not use if:

Users need to see total available records Counts drive reporting or business logic