how to remove the message "Number of rows removed from this list by Security constraints"

[CBunty]

I have a record level ACL which provides   read access to only the assigned groups and people part of assigned groups companies. It is working fine and only assigned groups and the department have read access to incident tickets

When I impersonate the user of a department I only see the tickets created in the department.

When I click on the module Open Incidents list results are spread across different list results. In some cases if the incidents are very new the first list results are empty but if we go through the list it shows in the last page.

I have 219 incident records and 50 incidents qualify for a department A. If   I impersonate the user from department A and click on Open Incidents module I only see 10 results and will have message as "Number of rows removed from this list by Security constraints:15". To see the next set of incidents I have to click on > or >> appearing below the list results. I want all the results to be appearing on the

[Mark Stanger]

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.

http://www.servicenowguru.com/scripting/business-rules-scripting/controlling-record-access-before-qu...

[amarjeet]

Hi Mark,

The self service users are not able to view the cmn_schedule table records in a catalog item , they are able to see "Number of rows removed from this list by Security constraints" .
How they will be able to see those records , please help.

thanks

[solonxu]

Hi CBunty, did you figure out the issue? I got the same problem. Available records should be pushed to first page but it didn't. Thanks.

[CBunty]

Yes the Business rule given in the link http://www.servicenowguru.com/scripting/business-rules-scripting/controlling-record-access-before-qu... will work but you have to adapt based on the requirements.