TM1 PAW - Exploration view - Insert calcul on 2 dimensions

[mrdauduong]

i think MDX option is still a better way because it is more flexible ! and i can add a variable instead of a element fixe!!

Hi Keith,

Edited:

I get what you mean, you just select from one dimension but from different blocks of the other dimension. Well, I never knew that worked.

I should thank Mr Duong for his persistence! Though I should add if he wants to makes this dynamic(que) then I presume the MDX option is the only way.


Maren

[Steve Rowe]

If you have a calculated measure of sufficent complexity that you need to make a MDX view, wouldn't you write a ruled measure or consolidation instead?

Put aside the relative complexity of a rule versus MDX and the level of rights you need to on the DB to undetake this activity.

I'm genuinely interested if there are use cases where an MDX view can deliver things that are not possible or obviously better than in a rule / consolidation?

I guess your MDX view can reference selections made in a users picklist cube and then alter the variance calculation based on what's selected. That variance calculation is only available in that view though.

If I did similair work in a rule sheet (or more likely a consolidation) then the variance is available for everyone everywhere all the time. I would have to create multiple variance measures though and the user would need to make sure they pick the right one for what they are looking at, so there is some complexity there that does not exist in an MDX view. I can also see how I could manipulate what is in the column set to cope with users navgating around using set MDX to get around this.

[Adam]

I'm genuinely interested if there are use cases where an MDX view can deliver things that are not possible or obviously better than in a rule / consolidation?

I've started a new thread: https://www.tm1forum.com/viewtopic.php?t=16328