List view shows no records: expected records not appearing

Active user filters or personalized list filters are hiding records from view, including saved filters or column-specific filters applied in previous sessions. (high likelihood)

Missing or restrictive read ACL permissions preventing the user from viewing records in the table, either due to role-based access or field-level security. (high likelihood)

Before-query business rules are filtering out all records during the query execution, often due to conditional logic or domain separation rules. (medium likelihood)

Domain separation is active and the user's domain does not have access to view records in the target domain or global domain visibility is restricted. (medium likelihood)

Table access controls or data policies are preventing record retrieval, or the table inheritance chain has broken ACL permissions. (low likelihood)

Step 1: Clear all active filters by clicking the filter icon in the list header and selecting 'Remove all filters' to eliminate any user-applied or saved filters.

Step 2: Reset the list view personalization by right-clicking the list header, selecting 'Configure', then clicking 'Reset to default' to remove any column or view customizations.

Step 3: Verify read access by navigating to System Security > Access Control (ACL) and searching for rules affecting the target table, checking if your user roles have read permissions.

Step 4: Test with an admin account or elevated privileges to determine if the issue is permission-related by impersonating a user with broader access rights.

Step 5: Check for active business rules by navigating to System Definition > Business Rules and filtering by the target table name, looking for before-query rules that might filter results.

Step 6: Examine domain separation settings at System Properties > Domain Separation to verify domain visibility and ensure the user can access records in the appropriate domains.

Step 7: Review the System Log at System Diagnostics > Log > Application Log for any ACL violation messages or query execution errors that occurred during list loading.

Step 8: Use the background script functionality in Scripts - Background to run a direct query on the table using GlideRecord to confirm records exist and are accessible programmatically.