Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Visible records shows on each page on list view with 'Number of rows removed due to Security Constraint' separately - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Visible records shows on each page on list view with 'Number of rows removed due to Security Constraint' separately
KB0718678

Visible records shows on each page on list view with 'Number of rows removed due to Security Constraint' separately


2480 Views Last updated : Jul 2, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

In a list view, if there are records spanning over multiple pages (or list is configured to show a certain number of records in each page), and the user is viewing those do not have access control to view all, they will only see the records that are allowed for them for each page separately. For all other pages, if they move to the same, access control will evaluate based on the records that are normally on the page and will hide others as per ACL. 

The system does not show all records by consolidating and evaluating ACL altogether. As the pagination goes on, records are displayed over each page distinctly. The user has to navigate to the relevant page, to find which record is visible to them.

Release

All

Cause

This behaviour is by design so that it does not impact the performance when executing the query for getting all the records together. By separating the ACL evaluation at each page level, SQL will only consider the records for the page and not all the records together. If it would do so, it would significantly reduce the performance

Resolution

Users can create a Before Query Business Rule, so evaluate and retrieve the records that specific users are supposed to view. This could only show the records without the Security constraint message, as it will already be evaluated.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.