Query Range ACL error

VullankiL
Tera Contributor

Hi All,

In my custom application, there is a table like "custom_requested_item".  And there is also another table like "custom_requested_item_aux".  There both tables have reference to each other.

So, In "custom_requested_item" table list view, If I try to filter the records based on the field which is present in "custom_requested_item_aux" table by dot-walking, then for all dot-walking fields it is throwing error like below: 

"Part of the query on custom_requested_item has been ignored because of insufficient access for 'query_range' operation on custom_requested_item.req_item_aux.field_name"

Currently, In "custom_requested_item" table, there are 2 query_range ACL for table.none, and table.* for role "public"
I have gone through some community links, where they have mentioned to create new ACL for that field. But in my case the issue is occurring for all dot-walked fields. what should I do now?
Where Do I need to create/update the query_range ACL.. Please suggest the solution..

Thank you

2 ACCEPTED SOLUTIONS

Yes , you can try doing that, I believe that should fix the issue.


Raghav
MVP 2023
LinkedIn

View solution in original post

vignesh parthib
Tera Guru

Hi @VullankiL 

 

Create query_range ACL for custom_requested_item.req_item_aux table, it should be very similar to the ACL present in custom_requested_item . That will fix your error.

 

Thanks,
Vignesh
"If this solution resolves your issue, kindly mark it as correct."

View solution in original post

5 REPLIES 5

RaghavSh
Mega Patron

I believe you will have to update the ACLs in "custom_requested_item_aux" table.

Look for Query range ACLs in "custom_requested_item_aux" table and update the roles.


Please mark the answer correct/helpful accordingly.


Raghav
MVP 2023
LinkedIn

Hi @RaghavSh ,

I have checked ACL's in the "custom_requested_item_aux" table. But there is no query_range ACL's present for this table.
Should I create it now for both table.none and table.*

Thank you

Yes , you can try doing that, I believe that should fix the issue.


Raghav
MVP 2023
LinkedIn

vignesh parthib
Tera Guru

Hi @VullankiL 

 

Create query_range ACL for custom_requested_item.req_item_aux table, it should be very similar to the ACL present in custom_requested_item . That will fix your error.

 

Thanks,
Vignesh
"If this solution resolves your issue, kindly mark it as correct."