Number of rows removed from this list by Security constraints: 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2017 11:48 AM
One of our managed documents users is receiving the below message on a filtered list of documents (filtered by type). I was able to reproduce what she's seeing by impersonating her. However, when I do the search on my end (I'm an admin), I do not see the same message. Also, I see the same total number of records (29). What does this message mean? Are there really 2 documents that are somehow hidden from her and me?
Message:
Number of rows removed from this list by Security constraints: 2
- Labels:
-
Legal Service Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2017 11:52 AM
Which table is she trying to access. There could be some ACL which is restricting access to this record.
Please mark this response as correct or helpful if it assisted you with your question.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2017 11:53 AM
Yes Elizabeth, there are 2 records that are hidden from the User. All you need is to look for read ACL on the managed document table & override it accordingly.
Security constraint Error: is mostly of ACL security while number after the statement shows number of rows hidden.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2017 11:53 AM
Check the ACL on that table. That user will not have all the role to access all record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2017 08:51 PM
The only time you'll see this message is when you're using a row-level read ACL for a table. Unfortunately there's no way around it using ACLs. The standard practice for securing a mixed bag of records for a table is to use a 'Before query' business rule instead. A good example of this in the OOB setup that you can follow is the 'incident query' business rule. I've written about this at SNGuru so you should find a good explanation here.