- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2025 11:49 PM
Hello all,
I have a glide_list field in a custom table where I added some choices. It works fine when I display it in the form, but when I display the field in a related table (another table that has a reference to the custom one), the field displays no choices (screenshot).
If I configure the reference of the glide_list to sys_choice and look for the choices there, then it works, but end users are then blocked due to ACLs.
What could I do to make it work? For me it looks like a bug, as choice fields work on related tables. Thank you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2025 04:51 AM
Hi @Sandeep Rajput,
I got the following answer from Servicenow:
"Glide List fields are fields that can hold many reference values at a time (as opposed to a reference field that holds just one value.) The most familiar example of a glide list is the Watch list field on the task table (incident, problem, change, etc.)
If you would like to select multiple choices, then you can create a custom table where you can store these choices in the table and then you can select the table in the reference specification to allow displaying the choices from there to show them in the glide list. "
It seems like they don't want us to use the glide_list field as a list of plain choices but rather as a reference to a table. Either way, thank you for your answer! I checked the ACLs but I imagined it was an issue related to how the field works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2025 12:54 AM
I have an issue with that an is that, for internal reasons, I cannot edit or create ACLs, so I was looking for a way of doing it just using the choices I created in the variable. We ended up leaving the requirement for now until we find a better solution for it. Thank you everybody for answering!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2025 04:45 AM
seems end users are not having read access to sys_choice table
Did you check which ACL is blocking?
May be some field level READ ACL on sys_choice is also blocked for those users such as sys_choice.value
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
02-25-2025 08:14 AM
sys_choice are not meant to be used in Glide List Field.
Glide List will save a reference to the choice's sys_id but sys_id for choice are NOT reliable:
Whenever you edit choice in an update set and commit the update set to another instance, all sys_choice for the table/field combo are regenerated, with new sys_id.
That means all your reference are lost.
