How to configure cascading filters in Platform Analytics Dashboard based on reference field values?

Sathwik1 · 3 weeks ago

Hello Team,

I'm working on a Platform Analytics dashboard in ServiceNow Australia (Patch 7). All reports on the dashboard use the kb_knowledge table.

I have configured two dashboard filters:

Category — Reference field to kb_category

Service Offering — Reference field to service_offering

Requirement:

When a user selects a Category, the Service Offering filter should dynamically display only the offerings associated with that selected Category. The relationship between Category and Service Offering is available through records in kb_knowledge, where both reference fields exist.

What I've tried:

Configured both filters using their respective reference tables.

Configured the Data to filter settings for both filters.

Enabled Follow other filters on the Service Offering filter, but the Category filter is not available to follow. The configuration shows that the filters cannot be followed.

Checked the Many to Many Definition (sys_m2m) table but couldn't find a matching relationship between kb_category and service_offering.

Questions:

Is it possible to achieve this requirement using native cascading filters in a standard Platform Analytics dashboard?

Can a Database View joining kb_knowledge, kb_category, and service_offering enable this cascading behavior?

Is there any supported way to dynamically populate the Service Offering filter based on the selected Category, possibly using a Script Include, without using UI Builder or creating a custom physical table?

I'm looking for a supported solution that works with a standard Platform Analytics dashboard.

@Ankur Bawiskar @Tanushree Maiti

jeffrubinoff · 3 weeks ago

Screenshots of your filter configurations would be useful.
I'm trying to follow what you have done by text, and I am having a little trouble with it. I don't see where you fulfil this condition:

The filter to be followed must filter data on the same table as the filter source of the following filter.

In the example in the documentation, the filter for incident assignment groups has the Group table as its filter source. It follows the Manager filter, which filters the Manager field on Group. So the filter that is doing the following has a filter source on one of the tables that the followed filter filters. (sorry)
I don't see this relationship in your description of your filters. What are the fields and tables under Data to filter on your Category filter? What is the Filter source on your Service Offering filter? A field under Data to filter on the Category filter must point to the same table as a filter source on Service Offering.

ashamanjuna · 2 weeks ago

Hi @jeffrubinoff

I’m configuring cascading filters in a ServiceNow Platform Analytics dashboard and need some help understanding why the Country filter cannot be followed by the City filter.

My requirement is to configure three cascading filters in this order:

Country → City → Office Location (i'm using cmn_location table here)

I’m using the following configuration:

1. Country Filter

* Filter source: Location.Country (field-based source, not the entire table)

* Data to filter:

* Location.Country

2. City Filter

* Filter source: Location.City (field-based source, not the entire table)

* Data to filter:

* Location.City

3. Office Location Filter

* Filter source: Location (the entire table, not a specific field)

* Data to filter includes:

* Interaction.Location

All three filters use the Pill UI element.

Issue:

The Office Location filter can follow the Country and City filters. However, the City filter does not list Country as an available filter to follow. In the City filter’s Follow other filters section, both Directly connected filters and Filters with table connection are empty, and the interface indicates that two filters cannot be followed.

I have already added Location.City to the Country filter’s Data to filter configuration, but this did not resolve the issue.

One difference I noticed is that the Country and City filters use field-based filter sources (Location.Country and Location.City), whereas the Office Location filter uses the entire Location table.

Could this behavior be related to the field-based filter sources, the field types, or a limitation in cascading filters when both fields belong to the same table? Is there a supported way to configure the filters to achieve Country → City → Office Location without changing the intended filter values?

Any guidance or suggestions would be appreciated.

Thanks!
Country filter configuration:

City filter configuration:

Location filter configuration: