TM1 Forum

How to achieve parallel hierarchy in TM1?
For example, I would like to create a dimension which has the following elements:


In exmple above, I have "Wages, Bonus and Others" as three different elements under three different parents. But TM1 considers all as the same elements. Will they take different values if entered as is? and If I delete one element, example - If I delete ' Bonus ' from under the OTHERS as its parent, won't this 'Bonus' element get deleted from other hierarchies as well ( Direct Labor and Indirect Labor)?
How to go about for this. ? Thanks a lot in advance

The only way to do what you want in TM1 is going to be give them all different names like Direct Labor Wages, Direct Labor Bonus...,Indirect Labor Wages...etc.

thanks for the reply tomok..
That option was anyways there (adding different names) but i don't think my customer will be satisfied with it.
I had a thought of creating aliases (which looks similar to the code I posted) but the original names will have different names
I was just thinking if it is possible in any other way.. of such parallel hierarchies.

hyd_ladka wrote:thanks for the reply tomok..
That option was anyways there (adding different names) but i don't think my customer will be satisfied with it.
I had a thought of creating aliases (which looks similar to the code I posted) but the original names will have different names
I was just thinking if it is possible in any other way.. of such parallel hierarchies.

Not possible... TM1 element names must be unique... and as Tomok said will only be achievable by using different variation of the name


ET

hyd_ladka wrote:thanks for the reply tomok..
That option was anyways there (adding different names) but i don't think my customer will be satisfied with it..

Tomok ... If you are presenting it to customer via e.g Active Form you could use an Attribute perhaps? (that will give customer an illusion that the names are the same).

EvgenyT wrote: Tomok ... If you are presenting it to customer via e.g Active Form you could use an Attribute perhaps? (that will give customer an illusion that the names are the same).

Thanks for the reply.
And thats what my idea was as well.. Not in Active form tho'.
I was just thinking of creating an Alias name and present it to the customer with the Aliases ON, so that he would have a feel that they are same names.
Thank you.

hyd_ladka wrote:

EvgenyT wrote: Tomok ... If you are presenting it to customer via e.g Active Form you could use an Attribute perhaps? (that will give customer an illusion that the names are the same).

Thanks for the reply.
And thats what my idea was as well.. Not in Active form tho'.
I was just thinking of creating an Alias name and present it to the customer with the Aliases ON, so that he would have a feel that they are same names.
Thank you.

Keep in mind aliases have to be unique as well, hence I said attributes....

Chand,
You can create different alias to Wages , Bonus and Other. But you cannot map different values to different alias. Still you can try..

Personally I find when a customer is extremely concerned about formatting etc that active forms in tm1web are usually the best way to go anyway, so that way you could go with what is probably also the most fundamentally sensible design of having different element names and then using an attribute to pull in what you'd like the users to see. You can then hide the column with the actual element names.

Another option(although certainly not my preference) would be to just separate it out into 2 dimensions.

This is probably a bit late, but why couldn't you separate the accounts and groupings you have into 2 dimensions? I'm thinking of a dimension simply being "Direct", "Indirect", etc. and the other one being the individual accounts of "Wage","Bonus", and "Other".

In your situation I don't believe you have a need for a second hierarchy in this dimension. Create a new Element in your measures dimension and put your new data there. Then you will be able to put data into the same hierarchy. It will make it much easier to switch between the two versions.

If you need to have a completely different hierarchy in this dimension, you can build a new hierarchy but the N-Level elements will contain the same data as the N-Level elements in the original, just roll up differently.

The reason you cannot have a parallel hierarchy as you describe is because elements need to be unique. Picture yourself in Excel, and you would like to write a DBRW to pull in wages. When you type "Wages" how would Tm1 know which hierarchy you are referring to in the dimension? There would be two elements with the same name but different data.