The problem is that, when you filter by multiple members of a dimension,
a calculated member gets created on that dimension, which goes in the
MDX "where" slicer, like:

Aggregate({[Manager1],[Manager2]})

But such a [Manager] member technically has no descendants, so your
calculated measure returns a count of 0.


The only work-around that I can think of is tedious (maybe someone else
in the group has a better idea):

- Create a second cube with the [Manager] dimension table as its
"fact-less" fact table, and only the [Manager] dimension. This may
require a bit of tweaking.

- Define just a Count measure like [WorkerCount]. I assume that each
table record corresponds to a leaf [Worker], so that this gives the
number of workers for any member.

- Combine the original cube and this cube in a virtual cube.
Define a calculated measure in the virtual cube like
ValidMeasure([WorkerCount]), so that it ignores dimensions other than
[Manager]. This returns the desired value.


- Deepak

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

That makes perfect sense as to why it is returning nothing. Is there any way to get to the MDX statement coming back from the OWC and use that in the calculated measure?

The virtual cube fix should work but I have several calculated measures using currentmember and I would need a cube for each.