Not able to use "current" in reference qualifier

surya76
Tera Contributor

‎03-23-2025 04:32 AM

I am encountering an issue in ServiceNow related to the reference qualifier for a catalog item field. Here are the details:

  • Field Name: Subcategory (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_category

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


OBSERVIARION:
1. When I use current in my reference qualifier. This issue persists and incorrect choices are populated.

2. When I don't use current in my reference qualifier., there is no issue.

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.

 

I am an English admin user.

0 Helpfuls
  • 730 Views
1 REPLY 1

Brad Bowman
Kilo Patron
Kilo Patron

‎03-23-2025 05:14 AM

When manually filtering a list view of the sys_choice table by the same criteria, using the category value you are testing with, do you see the same choices with the same values in various languages?  Do you see the correct Subcategory choices when testing the Catalog Item (without the UI Policy)?  If the choices are correct on the request form / RITM, but you can't create a UI Policy with conditions for the correct choices, then use a Catalog Client Script instead.

0 Helpfuls