With multi-select, typically a calculated member is created on that
dimension; so hierarchy functions like DESCENDANTS
([Product].CURRENTMEMBER, [Product].[Product Name]) won't work as with
single selections.
If you can't find an easier solution, this earlier thread discusses a
virtual cube approach in a similar situation:
http://groups-beta.google.com/group/...rver.olap/msg/
92a3c5104bc46402?hl=en
Quote:
|
MDX function does not working with multiple selection in OWC
|
...
The idea of the second [StoreMap] cube is that each individual leaf
Store can be tested against the Multi-Select Calculated Member, to see
whether it is included under the selected members or not. A copy of the
[Store] dimension is needed because the Multi-Select Member is selected
on [Store] itself, so the individual Store is selected along the
identical [StoreDup] dimension. The resultant [StoreCount] is only > 0
if the tested Store is a descendant of one of the multi-select [Store]
members. So only those leaf Stores lying under the selected members are
included in the [Sales < 5K] measure calculation.
...
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.developersdex.com ***