question Dynamic Location Filtering in Catalog Item based on Requestor, Role, and Stockroom (cmn_location) in HAM forum

Dynamic Location Filtering in Catalog Item based on Requestor, Role, and Stockroom (cmn_location)

LavanyaB8479798 — Thu, 19 Mar 2026 14:57:44 GMT

Hi All,

I am working on a ServiceNow catalog requirement where I need to dynamically filter a Location reference field based on multiple conditions like user role, requestor, hierarchy, and stockroom availability.

Scenario:

I have a Catalog Item with two Variable Sets:

Variable Set 1
- Field: Requestor For (Reference → sys_user)
Variable Set 2
- Field: Location (Reference → cmn_location)

🔹 Location Table Structure (cmn_location):

The hierarchy is as follows:

Region (e.g., APAC) → top level (parent is empty)
Country (e.g., India) → child of Region

🔹 Conditions:

I need to filter the Location field based on:

Location attributes:
- cmn_location_source = xxxxx
- cmn_location_type = xxxx
Stockroom condition:
- Only locations that have a related record in alm_stockroom (i.e., location has a stockroom)
User role:
- If user has itil role → show Region level (APAC)
- If user is end user → show Country level (India)
Requestor-based filtering:
- Based on selected Requestor For, restrict locations within the same hierarchy

🔹 What I Have Tried:

Created a Script Include (GlideAjax) to build dynamic query
Used Catalog Client Script (onChange) on Requestor For
Applied g_form.setReferenceQualifier() on Location field

🔹 Issue:

Since Requestor For and Location are in different variable sets,
I am unsure about the best approach to:

Trigger filtering correctly
Apply dynamic reference qualifier
Ensure it works across multiple catalog items

🔹 Questions:

What is the best practice to handle filtering when variables are in different variable sets?
Is GlideAjax + onChange the right approach, or can this be achieved using a reference qualifier?
What is the optimal way to filter locations based on:
- hierarchy (parent / parent.parent)
- stockroom availability (alm_stockroom)
How to make this reusable across multiple catalog items?

🔹 Any suggestions or best practices would be greatly appreciated.

Thanks in advance!

Re: Dynamic Location Filtering in Catalog Item based on Requestor, Role, and Stockroom (cmn_location

vaishali231 — Fri, 20 Mar 2026 07:36:16 GMT

hey @LavanyaB8479798

Approach

1. Variable Sets do NOT block access

Even though Requestor For and Location are in different variable sets, they are still part of the same catalog item form.

So you can safely reference:

g_form.getValue('requestor_for');

No special handling is required just because they are in separate variable sets.

2. Use Advanced Reference Qualifier

Instead of relying heavily on GlideAjax, the recommended approach is:

Use Advanced Reference Qualifier on the Location variable
Move all filtering logic into a Script Include

This keeps the solution:

Server-side
Performant
Reusable across catalog items

3. Centralize Logic in Script Include

Create a Script Include (non-client callable) that builds the encoded query.

Code:

4. Apply in Reference Qualifier

On the Location variable:

javascript&colon; new LocationFilterUtil().getLocationQuery(current.variables.requestor_for);

5. Handle Dynamic Changes (onChange)

If Requestor For can change after load, add a Catalog Client Script:

function onChange(control, oldValue, newValue, isLoading, isTemplate) { if (isLoading || newValue === '') { return; } g_form.setValue('location', ''); g_form.refreshReference('location'); }

This ensures the Location field refreshes with updated filters.

*************************************************************************************************************************************

If this response helps, please mark it as Accept as Solution and Helpful.

Doing so helps others in the community and encourages me to keep contributing.

Regards

Vaishali Singh

Re: Dynamic Location Filtering in Catalog Item based on Requestor, Role, and Stockroom (cmn_location

LavanyaB8479798 — Fri, 20 Mar 2026 13:10:48 GMT

Even after applying all conditions, I am still getting:

❌ Locations from other countries (e.g., United States)
❌ Locations not related to the requestor’s location (e.g., India)

Expected:

✔ Only locations under requestor’s hierarchy
✔ Only stockroom-related locations

Example:

Requestor Location → India
Expected → Only India child locations (sites with stockroom)
Actual → Getting locations from other regions as well