I might be wrong, but LOD's work basically using FIXED Dimensions. I don't think you can do that in Hierarchy. Again, I might be wrong.
What you can do to check if the hierarchy is exploded, is to count the nb or rows of the table and compare it to the size of Name . If equal you use one lod otherwise you use the other.
You get the number of rows with
WINDOW_MAX( index() )
computed table down
the size of Name with
compute along Name
and the final calc would be
if [nbRows] = [NameSize]
then SUM([LOD Fixed by Name (Denominator)])
else SUM([LOD Fixed by Name & Place (Denominator)])
it is a nested calculation , make sure to set the computing on both calc
CountD Sample(mc).twbx 24.8 KB
That was Great!!! Learnt a new thing Today from you.
Thanks Deepak !
This one works because the different calculations used are lods.
Unfortunately, if we use the same table calculation but we want to apply a different computing depending on the level of the hierarchy, we are still stuck.
Yes, What you finally Created was my initial thought also, but Somehow, I was missing on how to Switch over LODs. Anyways, It was Good Stuff from you as Always!!!