How do I prevent the "Rows removed by security constraint: x" Message from being displayed?

[cybernetic_crab]

In this Knowledgebase article, the author recommends to build an On Before Query Business Rule to filter the records that should not be displayed, so the list renderer would not have to decide wether the record should be displayed. Now I don't fully understand how to code the script for this rule, as any Queries on the current GlideRecord object would trigger the Script to be run again.

The problem that I am facing is that we have to separate groups working on Security Incidents, and neither should have access to the other's data. After implementing the access restriction, the users now see the message "Rows removed by security constraint: x". What I would like them to see is their own data, without the message and any hidden rows. The current implementation is not user friendly:

[cybernetic_crab]

Hi Chuck,

I see what you're implying.

The problem we have is that people who are trying to look at the table are not seeing any data unless they click on show next page multiple times. I just want to remove the empty rows, so that the data is visible where it should be.

[srikanthvk · Accepted solution]

Hi Leon,

You can disable the ACL for a while, use filter to see the records as per your condition. Right click on the filter to copy query and use it as an encoded query in the query business rule.

Hope this helps.

Please Hit like, Helpful or Correct depending on the impact of the response

Thanks,

Srikanth Varma

[cybernetic_crab]

Hi Srikanth,

I got there myself by now, but your solution is the right one 🙂 My problem before was that I tried to use .addQuery() instead of .addEncodedQuery().

Thanks for the help, much appreciated!

[shubham5957]

hi friend, i was also facing the same issue in which user have to click on next next to view the records in list, it is because acl had disabled the records for the list based on the number(in my case) so what i did i modified the sort sequence for that particular module. In my case if i sort number(a to z) it will not show but if i sort number(z to a) it will show the list of records on first page itself.  so basically i added this syntax in my argument under link type of that module and it works for me

&sysparm_order=sys_created_on &sysparm_order_direction=desc

i hope this will work

 

[shubham5957]

but yes coming back to your original question how to remove that message.. i am still working on it.. BR before query did not work in my case as it does not fulfill my requirements. if you were able to remove it please sahre with us. That would be great. Thank you..!!