Cascading filters on choice values on new Platform Analytics dashboards

[Ryan Monsen]

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.

This essentially allows for a drilldown into dependent choice fields.

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.

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

[jeffrubinoff · 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.

[Ryan Monsen]

Much appreciated, Jeff! I'm glad to know it's a recognized feature gap, and hope that it will be prioritized as an enhancement before the old dashboards are deprecated.

[Ryan Monsen]

Separately, I know you asked "how", but the second logical question is "why the heck is this so important to you", and I want to provide an answer there as well.

• A very basic example is given here - wouldn't it be nice to have the "subcategory" filter only show the subcategories relevant to the "category" filter option already selected? We've had dependent choice values forever, and it's mildly concerning that such a basic functionality would not be supported in Platform Analytics.
  
  
• You already linked the thread talking about VPs and Managers of groups. As mentioned by that thread's OP, "The goal is for the VP filter to also filter the list of Managers, so that you do not have to scroll through all managers to find only those under the selected VP." As I mentioned on that thread - so long as the filters are properly built on the sys_user_group table rather than sys_user, the relationship from VP to Manager is defined through the group table itself and is therefore well-defined.
  
  
• Finally, my example is a little more complex, but I am essentially trying to do group filtering as well. We have multiple choice-field levels of walkdown to allow us to report on subsets of groups (these fields are also used for e.g. SLAs). Sure, we have Group Managers who are actionable leads for escalations and such, but there are levels above them who may need to keep an eye on the metrics from a more bird's eye view. I could create individual dashboards for each level and area, ensuring the filters are correct and updating every single one when some new metric shows up... or I could do something like the below and say "Here is your working dashboard for Incidents. Filter as needed. Everyone is looking at the same data."