question Visibility on Group Names Catalog Item dropdown table reference field in Community Central forum

Visibility on Group Names Catalog Item dropdown table reference field

sireland — Sun, 19 Oct 2025 02:10:12 GMT

We have created a dropdown reference field in a catalog item to pull from the sys_user_group table in ServiceNow and pull the name as the actual field in the dropdown. I have now checked the ACl's and attempted creating a new one, I also tried to do a client script with no luck. I am trying to figure out what else I can do to get the visibility to work correctly. I followed the instructions in the known error page to no avail. The filtered options are visible to users with the business stakeholder role and other elevated roles, but not snc_internal. Please let me know if you have any suggestions or tips to resolve this issue. Thank you! https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0825813

Re: Visibility on Group Names Catalog Item dropdown table reference field

AndersBGS — Sun, 19 Oct 2025 04:48:47 GMT

Hi @sireland ,

have you verified that the snc_internal can see the table data from backend? If they can’t, then it’s an ACL restriction where you need to give a read permission to snc_internal for the table./ field level

Re: Visibility on Group Names Catalog Item dropdown table reference field

sireland — Sun, 19 Oct 2025 17:23:47 GMT

Dear Anders,

Unfortunately, I have checked all ACL's on sys_user_group table and confirmed with the access analyzer. That's why I don't know if I need to add another ACL as the documentation in the known errors article said, but it didn't work when I tried that previously. Thank you!

Sincerely,

Re: Visibility on Group Names Catalog Item dropdown table reference field

ashleyharve — Tue, 28 Oct 2025 19:42:16 GMT

I’ve struggled with similar visibility issues when configuring catalog items in ServiceNow. The key was ensuring user criteria aligned with both the catalog and category access settings. Sometimes even minor mismatches between group names or duplicated conditions can hide the dropdown unexpectedly. Reviewing ACLs and refreshing the catalog client script solved it completely.