Intersection cube calculation in Performance Modeler

[msnoriko93]

Hello, I'm new to TM1 and still learning little by little.
Anyway, my boss decided to move older application that was made from TM1 to Performance Modeler, and I'm stuck at writing intersection rules.

In TM1, we can write the rules as:

['Dimension1_Element1','Dimension2_Element1']

I was wondering if someone can help me how to write this rules in Performance Modeler.
Thank you in advance,

[Wim Gielis]

Hello,

I may be missing something but can't you just write rules in PM like in Perspectives / Architect ?

[qml]

I was wondering if someone can help me how to write this rules in Performance Modeler.

You can create and edit rules in the Model Design pane of Performance Modeler, similarly to how you would do it in Perspectives/Architect.

Rule syntax is unchanged and in your example the correct are definition would be as follows:

Code: Select all

['Dimension1':'Element1','Dimension2':'Element2']

If this does not answer your question then I'm afraid you'll have to rephrase it as it is not entirely clear what you are asking about.

Oh, and last but not least, you can tell your manager that he made a decision to migrate to a technology that is an evolutionary dead end. My suggestion would be to stay on the Perspectives/Architect dev stack until Prism a.k.a. Planning Analytics is prime time ready and has full development capabilities.

[msnoriko93]

I was wondering if someone can help me how to write this rules in Performance Modeler.

You can create and edit rules in the Model Design pane of Performance Modeler, similarly to how you would do it in Perspectives/Architect.

Rule syntax is unchanged and in your example the correct are definition would be as follows:

Code: Select all

['Dimension1':'Element1','Dimension2':'Element2']

If this does not answer your question then I'm afraid you'll have to rephrase it as it is not entirely clear what you are asking about.

Oh, and last but not least, you can tell your manager that he made a decision to migrate to a technology that is an evolutionary dead end. My suggestion would be to stay on the Perspectives/Architect dev stack until Prism a.k.a. Planning Analytics is prime time ready and has full development capabilities.

I mean how to write that rule in cube calculation from performance modeler.
but anyway, thank you. I'm going to try the one you told me.