![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
I would put the conditional counting into a view that underlies your parent child dimension. If how many is greater than zero then output a 1 else a 0 inside your view. Then you could create a new cube that consisted of just your parent-child dimension and summed up this new conditionally counted measure. You could then via virtual cubes tie this cube and your other cube together. In the virtual cube, you would need to create a calculated measure that wrapped your new measure in the ValidMeasure function so that it can be displayed even when it's sliced my dimension that are not in its base cube. This should give you excellent performance as the measure is now completely aggregatable. |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Hi Mario, Can you explain the the calculated [Measures].[How Many] - is it related to cube base measures, in a way that the condition: [Measures].[How Many] > 0 could be derived? - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
#6
| |||
| |||
|
| Count(NonEmptyCrossJoin(Generate([Customers].Members, |
![]() |
| Thread Tools | |
| Display Modes | |
| |