Users see "Number of rows removed from this list by Security constraints" message at end of list. - Support and Troubleshooting

Users see "Number of rows removed from this list by Security constraints" message at end of list. Description  Sometimes non-admin users might see the message “Number of rows removed from this list by Security constraints” at end of the page in a list.

Many times when a user views a list or report, the pagination shows 10/20/50 rows but only a limited number of rows are actually visible to user on the page.

At end of page the message “Number of rows removed from this list by Security constraints” is displayed with indication of how many numbers have been "hidden" on the page.

This may apply to many of the pages of the query results, it might be necessary for the user to navigate through a number of pages to find the required record if the result set is long but many of the records should not be visible to the user.

The user might find this quite confusing, however it should be possible for the user to apply a filter condition to the list to find a specific record (as long as they have read permission).

For example:

Release or Environment All

Cause This behavior is expected and as a result of the way that ACLs are applied in the list. The current design is to first execute the query against the table and retrieve all records that meet the specified filter condition, then for each row on the current page any read ACLs are evaluated to verify if the current user is allowed to view the record. If the user is able to view the record it is displayed as a row in the list, however if the user is not permitted to view the record it is not displayed. If there are any row that were not displayed the count is displayed with the message "Number of rows removed from this list by Security constraints"

Resolution This is our design and expected behavior of platform.

If your users are experiencing similar behavior or complain that "there are no records displayed" in a list, please evaluate if the issue is related to this behavior. It might be necessary for you to educate your user why this is happening.

Additional Information Very often it is possible to avoid this situation by using a before query business rule to restrict which records the user can see at the time that the query is executed against the database.

The feasibility of this as a solution will largely depend on the complexity of the restrictions that you want to apply to the visibility of the records eg. not everything could be implemented as a filter conditions on the SQL query.

For more information please see following knowledge article:

KB0523826 Before Query Business Rules - The *Other* Access Control https://hi.service-now.com/kb_view.do?sysparm_article=KB052382