- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 04:42 AM
There is a reference field "Name" in my catalog which is referencing to a Custom table, and its value is being displayed on the basis of selection of other variable which is choice field. For Non-Admin users it's showing NO MATCH FOUND on Portal view but it is working on classic view. For Admin users working fine on both the views.
Cross checked the ACLs nothing is there the role which is required to access the table users have those roles and can access the table and see the data.
Solved! Go to Solution.
- 942 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 04:57 AM
Hi @Sahil_kashyap
I believe it's beacuse of query_range ACL which has been introduced by ServiceNow recently.
To overcome this, you need to create one custom query_range ACL on your custom table.
Ex:
Regards,
Siva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 04:51 AM
so you are applying some reference qualifier to show the values?
is it calling a script include?
For non-admins how it's behaving in classic view?
Any query business rule on that custom table?
share some screenshots.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 05:05 AM
using Reference qualifier calling script include, for non-admins it's displaying values as expected
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 05:09 AM
was this working fine earlier?
for non-admin it's working fine in classic but not in portal?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 04:57 AM
Hi @Sahil_kashyap
I believe it's beacuse of query_range ACL which has been introduced by ServiceNow recently.
To overcome this, you need to create one custom query_range ACL on your custom table.
Ex:
Regards,
Siva