Blocking Query_range ACL for non-existing field?

[kim-lindgren]

I have created a list report on the cmn_notif_device table. There is a related list condition in the filter set to the following:

---

Now when I impersonate the user who should be able to access it via a read ACL, I get the following error message: 

Part of the query on cmn_notif_device has been ignored because of insufficient access for 'query_range' operation on sys_notif_subscription.devices

I thought then that I should simply set up a query range ACL for the table "sys_notif_subscription" and the field "devices" - but this field does not exist on that table.

What am I missing here?

Best regards,

Kim

[Tanushree Maiti]

Hi @kim-lindgren 

Just create a query_range ACL on table field level sys_notif_subscription.devices .

ACL role- set as Public until and unless you have specific role, which you need to assign separate to user .

[John Gilmore]

To provide a little more detail on what is happening the cmn_notif_device table has a reference to sys_notif_subscription and your query is trying to use that reference to pull/display the devices field from the referenced record. In order for the query to do so the user must have query_range permissions on the field/attribute of the referenced record and it does not based on the error.

If your organization is comfortable with it you should just be able to add the query_range ACL at the table level on sys_notif_subscription.

If you need it at the field level then "devices" is the actual field name for the field labelled "send to". So when trying to set the field level ACL you may be seeing the label instead of the field name so look for "send to".