- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2025 01:23 PM
We have created a Record producer for maintenance work for a client. We have created a custom table to store the data from the form. On the record producer, we have a reference field that references a custom location table. This custom table is not extended from any other tables. We are currently in the dev environment. There are three roles created for the table (viewer, editor, admin). The u_location_address field on the table is set to the display value. There are 2 Business Rules created for the table. Neither have any intended effect on the u_location_address field.
Problem:
When accessing the form as an admin, the location field on the form performs as it should. It allows access to the table. However, when accessed by another user who has any of the table specific roles (viewer, editor, admin) the field returns a "no matches found" result.
However, when I remove the display value from the table (eg no display value set for the table) it returns results from the "created" field for all users that have access to the table.
I have attempted to remediate the issue by setting a different display value, re-created roles, checked ACLs etc but the form still performs incorrectly.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2025 05:45 AM
Thanks for the replies all. I worked with ServiceNow and they confirmed that it was not an issue with my read ACL. The problem was with query_range ACL. I was instructed to create a query_range ACL for the display field (u_location_address), which worked perfectly.
Thanks all for your support