How to configure a cascading Interactive Filter for Service → HR Service → HR Category ?

[prash4]

How to configure a cascading Interactive Filter for Service → HR Service → HR Category on a Universal Request dashboard?

I am trying to configure a Cascading Interactive Filter on a ServiceNow dashboard based on Universal Request [universal_request].

My Requirement is 
Service
↓
HR Service
↓
HR Category

The expected behavior is:

When Service = HR is selected, the relevant HR Services should be available.
When an HR Service is selected, the HR Category dropdown should dynamically display only the categories related to that HR Service.
For example:
Service = HR
↓
HR Service = Benefits
↓
HR Category =
Benefits Appeal
Benefits Enrollment/Removal
Dependents/Beneficiaries
If the user changes the HR Service to Employee Documents, the HR Category list should refresh and show only categories belonging to Employee Documents.

The fields are on Universal Request:

Service: u_service
HR Service: u_hr_service
HR Category: u_hr_category
The underlying relationships are:

HR Service → Service
HR Category → HR Service
I have created a Cascading Filter with three levels

Service
└── HR Service
└── HR Category
However, I am not sure how to correctly configure the Table, Display Field, Parent Reference Field, and Target Tables for each level.

[musislam]

Hi @prash4 

I think the mix-up is which table each level points at. The levels aren't built on universal_request, that table only shows up in the Target config at the end.

Level 1 is Table = your Service table, Display field = name. Level 2 is Table = HR Service, and Parent Reference Field is the field on the HR Service table that points back at Service. Level 3 is Table = HR Category, Parent Reference Field = the field on HR Category that points at HR Service. Then under Target you add Target table = Universal Request and the Field to filter on, one per level, which is where u_service, u_hr_service and u_hr_category go.

The catch that would stop this dead: only reference fields work in cascading filters, and only Single Select. If u_hr_category is a choice field rather than a reference, no amount of level config will make it cascade. Same on the source side, HR Category needs a real reference field to HR Service, not a category string.

You will also need hp_publisher_admin and report_admin to create it.

1. Are u_service, u_hr_service and u_hr_category all reference fields, or is any of them a choice?

2. Is this a Platform Analytics dashboard or a classic one? The config differs and I have only confirmed the Platform Analytics side.

3. What tables are HR Service and HR Category pointing at, OOB sn_hr_core_service or custom ones?

4. Does the HR Category table have a reference field to HR Service, or is the relationship held somewhere else?

If that works for you, mind marking it as the recommended solution? Helps me support these better for the community.

[prash4]

Hi @musislam, thanks for the response,

three fields are choice fields on Universal_request table 

working on classic reports 

i have a report admin role