Reference qualifier affects the UI policy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2025 02:41 PM
I am writing to seek assistance with an issue I am encountering in ServiceNow related to the reference qualifier for a catalog item field. Here are the details:
- Field Name: Category (a lookup select box field pointing to the sys_choice table)
- Reference Qualifier Used:
javascript:'name=sc_req_item^element=u_sub_category_^inactive=false^dependent_value=' + current.variables.itsm_subcategory
Issue: When I create a new UI policy and include this category field in the condition, the choices displayed are in a different language. However, when I use the following reference qualifier, the correct choices are displayed in the UI policy:
nameINjavascript:getTableExtensions('sc_req_item')^element=u_sub_category
I would appreciate any insights or solutions you could provide to resolve this issue. Specifically, I am looking to understand why the first reference qualifier causes the choices to display in a different language and how to ensure the correct choices are displayed consistently.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2025 09:47 PM
you are with English admin user.
It should not impact ideally as the field in UI policy will bring choices from sys_choice table without any dependency
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
03-23-2025 04:22 AM
No, this happens whenever I use current.variables in my reference qualifiers in catalog variable.
if don’t use the current.variables in my reference qualifiers the choices are populated as expected in english
i have attached a choice when choice populating incorrect