In June, there was a blog post by Kevin Donovan (Program Manager for PerformancePoint Services) describing new features coming in SP1 for PerformancePoint Services. PerformancePoint Services are a part of SharePoint Server 2010. The most exciting feature introduced in his post is “Cascading Filters”. Cascading filters are the number one enhancement request for the Text Search Filter for PerformancePoint.
Cascading Filters is a concept that allows you to take the selection of the first filter and use it to limit the choices in the second filter. The second filter would only have items populated in it based on the selection from the first filter. Filters then cascade until finally the output is used for a report. Basically, this is a guided drill down process.
For more description on how cascading filters work, check out PerformancePoint 2010 Cascading Filters. For the full example described in this post, review PerformancePoint Services 2010 – Cascading Filter Example.
Following the examples in my previous posts, I have shown below how to “link” or cascade two filters together. See the image below. In this example, there are two filters in a PerformancePoint dashboard header. The “state” filter passes a value to the “county” filter. Based on the selected state, only the counties from that state are displayed in the county filter.
In general, this process works for multidimensional filter types – Member Selection, MDX Query, and Named Set filter types.
For another example, check out Dan English’s BI Blog post.