- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Community,
We’re currently using the cmdb_ci_service table as a reference for one of the variables in a catalog item. However, end users (who do not have any roles) are unable to see the dropdown values in the reference field.
Here’s what we’ve tried so far:
- Created ACLs on the cmdb_ci_service table to grant read access to authenticated users.
- Tried similar logic via ACL scripts to check if user is logged-in.
Despite these efforts, the reference field remains empty for end users. What could be the possible root cause for this issue? Are there any overlooked ACLs, table-level permissions, or catalog-specific constraints that might be preventing the dropdown from populating?
Any insights or suggestions would be greatly appreciated!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
it has worked in recent month for something similar issue.
Reference variable not visible in Portal for non-admin user but visible in classic view
Did you try creating Table.None query_range ACL?
see this article
Ways to analyze and fix the query_range issue in portals using Access Analyzer
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
3 weeks ago
it has worked in recent month for something similar issue.
Reference variable not visible in Portal for non-admin user but visible in classic view
Did you try creating Table.None query_range ACL?
see this article
Ways to analyze and fix the query_range issue in portals using Access Analyzer
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
3 weeks ago
table.None works, thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Srashti Sharma ,
The issue is usually due to missing read ACLs on parent tables. Even if cmdb_ci_service has ACLs, end users also need read access on cmdb_ci and cmdb. Check those ACLs and any reference qualifiers if the parent ACL blocks access, the dropdown will stay empty.
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @M Iftikhar ,
Thank you for the response. I tried giving access to the cmdb_ci read acl as well but it is still not working.
Thanks,