Using Performance Points scorecards as filters to solve cascading dropdown and row count issues

One of the criticisms often levelled at Performance is the lack of cascading dropdowns. Not when selecting from a single hierarchy (which PPS does quite well, up to a soft limit of 5000 members), but when attempting to cross filter.

For instance, in our example from the Adventure Works database, we may want to initially select bike racks from the product subcategory hierarchy of the Product dimension, and then only have 2007 and 2008 years of the date dimension available as bike racks were not sold in 2005 and 2006. In order to do this, we of course need to filter by a measure, in this case Sales Amount works nicely.