- 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
By default, cmdb_ci_service CIs are accessible to all users. We experienced the issue after activating Continual Improvement Management (CIM) plugin. CIM application introduced two new read ACLs on cmdb_ci_service table.
We end up deactivating those two read ACLs which fixed the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi Swapna, thank you for your response. Previously, we didn’t have an ACL for cmdb_ci_service, and end users couldn’t see the dropdown. Now that we’ve created the ACL, end users can see the dropdown in native view, but it’s still not visible on the portal.
Thanks,
Srashti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
are they able to see in native by navigating to cmdb_ci_service.LIST ?
If yes and not showing in portal then issue is due to query_range ACL
Create 1 query_range Operation ACL on your table.* and give the role you want
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
Hi @Ankur Bawiskar,
Thank you for the response. End users are able to see records on native by navigating to cmdb_ci_service.LIST. I tried creating the query_range ACL but it does not seem to work.
Thanks,
Srashti