Hi there,

I am facing a very big problem related to the scorecard filter connection.

I have a dimension hierarchy in the rows of the scorecard and I have a Filter connected to that hierarchy. The filter contains 2 members: "All" and "Active".

"All" should show all the dimension hierarchy members in the scorecard 

"Active" should show only the hierarchy members that have as True the "Active" member attribute.

This requirement is done, but the PROBLEM is that when I connect the filter to the scorecard, the scorecard is no more showing a hierarchy with the expand and collapse controls in the members, instead, the scorecard is showing a "flat" set of the hierarchy without levels and expand and collapse controls.

The filter connection in the scorecard has a connection formula as following:

IIF(<<SourceValue>>.Member_Name = 'Active', (([MyDimension].[MyDimHierarchy].Members,[MyDimension].[Active].&[1]), [MyDimension].[MyDimHierarchy].Members)

Is there any way to get the hierarchy filtered without loosing the hierarchy shape and behaviour? Maybe the connection formula above is not 100% correct for filtering a hierarchy...

Thanks and best regards,

Joss

If you are using a hierarchy in the scorecard and connect with a filter you will lose the expand/collapse of the hierarchy, but you will still be able to drill up/down in the hierarchy.  This has been noted in a few other threads as well already and I have not seen any hotfixes for this issue at all:

Expand/Collapse in a Scorecard - SharePoint 2010 (http://social.technet.microsoft.com/Forums/en-US/ppsmonitoringandanalytics/thread/8330c17a-6dd0-4423-8609-424813d466e1)

Filtering dynamic hierarchy in PPS 2010 scorecard (http://social.technet.microsoft.com/Forums/en-US/ppsmonitoringandanalytics/thread/50d4aaaa-208b-490d-920f-73bd1eb1f35a)

While this is a bit late...

I found what Dan English said to be true in PerformancePoint 2010.  However, my source cube also exposed the same values used in the row hierarchy of my scorecard under separate attribute hierarchies, so I used those values in the filters and it got me around this issue.

For example:

Scorecard uses a [Product Categories] hierarchy containing the levels [Category], [Subcategory], and [Product] on the rows.  Instead of creating a filter to [Product Categories].Category.Members, I used [Category].[Category].Members and connected this to the Scorecard at the Page level.  In my case, I was using cascading filters, so I repeated with the filter for Subcategory and Product.  This seemed to work as I desired if anyone else wants to give it a try.