Cascading filters on choice values on new Platform Analytics dashboards

Ryan Monsen
Tera Contributor

Hi all,

In Performance Analytics Responsive Dashboards, I have created a Cascading Interactive Filter which allows to filter the same table by dependent choice values.

 

RyanMonsen_0-1729533418159.png

 

This essentially allows for a drilldown into dependent choice fields.

RyanMonsen_2-1729534049972.png

 

 

I cannot find a way to mimic the same in new Platform Analytics dashboards. Creating filters on Choice 1 and Choice 2, for example, I cannot have Choice 2 filter follow Choice 1. It seems like the following filter has to be a reference field and not another choice value.

 

RyanMonsen_1-1729533816182.png

 

Is there a way to accomplish a cascading filter by choice values in new Platform Analytics dashboards? Thank you.

 

1 ACCEPTED SOLUTION

Ryan, I've chatted with several devs and the senior PM. The PM says they have heard about this from other customers as well, and it's a recognised feature gap with the old filters. Unfortunately, I cannot tell you anything more concrete than that at this time. @Thomas Davis might be more likely to know of any plans as they develop.

View solution in original post

7 REPLIES 7

Steve McCulloug
Tera Contributor

Also seeking a solution to this.

jeffrubinoff
ServiceNow Employee
ServiceNow Employee

You both seem to have the same problem that was discussed in this thread: https://www.servicenow.com/community/platform-analytics-forum/platform-analytics-cascading-filters/m...
The answer is the same: you cannot filter fields by other fields, only records by fields. The devs would like to know more about how you implemented this on Cascading interactive filters on responsive dashboards, because they didn't know it was possible.

Hi Jeff, thank you for your reply! I'm going to set up a similar example with out of box fields to explain. We'll create a Problem Filter for Incidents. To test this, you'll need to go fill out subcategories for the Problems attached to the OOB Incidents, as none of them are filled out. 🙂

 

SETUP:

 

We'll start by creating a Cascading Filter.

RyanMonsen_0-1734543780970.png

 

The first level will be Problem Category.

RyanMonsen_1-1734543795195.png

After we create this, a Target table record should be created that applies to the Incident's Problem.Category:

RyanMonsen_2-1734543824907.png

 

The second level will be created under this cascading filter:

RyanMonsen_3-1734543839513.png

 

 

When setting up Problem Subcategory, notice how the Parent Reference Field is Category. This is the field referenced by the cascading filter, but Category is not a "reference field" - important distinction.

 

RyanMonsen_4-1734543847481.png

 

A similar Target table record should be set up for this filter, this time looking at the Incident's Problem.Subcategory.

RyanMonsen_6-1734543939258.png

 

The third level is the Problem itself, created under Problem Subcategory, and I've set the display field here as Number. The Target table entry for this is simply the Incident's Problem field.

RyanMonsen_7-1734543981190.png

RyanMonsen_8-1734544004774.png

 

 

TESTING:

 

I've created a very basic report, "Every Incident with a Problem" (Problem is not empty), and added to a Dashboard with the Cascading Filter.

As I mentioned above, various Problems need to have subcategories added to them for proper testing.

 

Unfiltered:

RyanMonsen_9-1734544057264.png

 

Filtering just to the first level, Category:

RyanMonsen_13-1734544535779.png

 

RyanMonsen_10-1734544076519.png

[{"aaf4f729c3221210dca0171ed401311b":[{"table":"incident","filter":"problem_id.category=software","allow_extended_table":true,"allow_database_view_filter":false}],"selectedFilters":{"aaf4f729c3221210dca0171ed401311b":{"field":"category","value":"software"}}}]

 

 

Filtering to the second level, Subcategory, where you notice only Subcategories relevant to Category = Software are selectable:

RyanMonsen_14-1734544561986.png

 

RyanMonsen_11-1734544091030.png

[{"aaf4f729c3221210dca0171ed401311b":[{"table":"incident","filter":"problem_id.category=software","allow_extended_table":true,"allow_database_view_filter":false}],"e5357f29c3221210dca0171ed40131d3":[{"table":"incident","filter":"problem_id.subcategory=os","allow_extended_table":true,"allow_database_view_filter":false}],"selectedFilters":{"aaf4f729c3221210dca0171ed401311b":{"field":"category","value":"software"},"e5357f29c3221210dca0171ed40131d3":{"field":"subcategory","value":"os"}}}]

 

Filtering to the third level, Problem, where only Problems relevant to Subcategory = Operating System are selectable:

RyanMonsen_15-1734544601225.png

 

RyanMonsen_12-1734544109613.png

[{"aaf4f729c3221210dca0171ed401311b":[{"table":"incident","filter":"problem_id.category=software","allow_extended_table":true,"allow_database_view_filter":false}],"e5357f29c3221210dca0171ed40131d3":[{"table":"incident","filter":"problem_id.subcategory=os","allow_extended_table":true,"allow_database_view_filter":false}],"b7557f29c3221210dca0171ed40131ef":[{"table":"incident","filter":"problem_id=46eaa7c9a9fe198100bbe282da0d4b7d","allow_extended_table":true,"allow_database_view_filter":false}],"selectedFilters":{"aaf4f729c3221210dca0171ed401311b":{"field":"category","value":"software"},"e5357f29c3221210dca0171ed40131d3":{"field":"subcategory","value":"os"},"b7557f29c3221210dca0171ed40131ef":{"field":"sys_id","value":"46eaa7c9a9fe198100bbe282da0d4b7d"}}}]

 

 

Thank you, Ryan! The dev I wanted to show this to in particular is on holiday until January, but I will be certain to show it to him then. No promises, of course, but I hope we are able to do something in the name of feature parity.