Data Filtration Security Constraints message "Number of records removed..." and Pagination
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2024 03:54 PM
Client do not want the Security Constraints message that shows how many number records are removed because the current logged in user is denied of access ("Number of records removed due to security constraints...") also the Pagination showing number of records in total but removing the records they are denied of access to. We are looking for something that do not show this message however On Before query is giving us performance issues so we're looking at this "Data Filtration" however it also shows this security constraints message. I this something we can't disable both for ACL and Data Filtration?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2024 05:09 PM
Hi @ryev_a_ ,
If thats the case then we should work on the indexing, which could improve the performance.
One other way is to simplify the BR , especially avoid multiple loops and using an efficient query.
Also as Drew suggested you should involve ServiceNow team here to analyse your issue better, try raising a HI Case.
If my response has resolved your query, please consider giving it a thumbs up ‌‌ and marking it as the correct answer‌‌!
Thanks & Regards,
Sanjay Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2024 05:12 PM
Yes we've been trying to optimize it. I'll try to raise a question to SN support as well.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-23-2024 06:30 AM
Ok so one option is to create a field on the requested item table called something like "Cat Task Assigned to" and then any time a cat task assignment is updated you can then just update that field. This will allow the system to query without having to do any joins or subquerys and should be faster. It does mean that you will have more moving parts so you will have to decide if that is worth the performance increase you get.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-23-2024 02:42 PM
Thanks, We also thought of this, adding a new field in request form just to put user assigned to related records, this will also include running this logic one time to populate older records and that will also mean the last update of all the records will be the one who runs the script and then last update date will all be the same, I am not sure client will like this for audit reasons.