- 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-25-2025 04:42 AM
@AlexLF96 This looks like an ACL issue to me. Did you use the Access Analyser to test if your user has access to the custom via a read ACL?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2025 04:48 AM
Hi @Sandeep Rajput,
I created a ticket for Servicenow support and got the following answer:
"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 are not expecting users to use a glide_list field with sys_choice choices. There is not much we can do, but thank you for your answer!
- 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-25-2025 06:35 AM
@AlexLF96 We have used sys_choice as a reference in GlideList successfully in past. ACL do pose a challenge in this case, However, they can be easily tweaked to allow end users to have access to the choices.