Is TM1 dimension index important?

Post Reply
Posts: 1
Joined: Wed Nov 08, 2017 8:58 am
OLAP Product: TM1
Version: 10.1.1
Excel Version: Excel 2013

Is TM1 dimension index important?

Post by zyzhang6 » Wed Nov 29, 2017 2:12 am

Hi Everyone,

Please forgive me ask this stupid question. I just shift the system from Oracle HFM to TM1. There is one thing I am quite confuse at TM1 is about the dimension index. In HFM, when I write calculation rule, I always use the parent-child relationship to identify the elements involve in a calculation. For example, run this rule at all base accounts under "Total Assets". I do not need to take care about the exact index number of the element.

May I know whether this is the same case in TM1?



Posts: 41
Joined: Fri Feb 15, 2013 5:49 pm
OLAP Product: TM1
Version: 11.2
Excel Version: 2016

Re: Is TM1 dimension index important?

Post by ascheevel » Wed Nov 29, 2017 7:17 am

You would write the rule in TM1 similar to how you did it in HFM, you don't need to account for the element index. In TM1, you can use ELISANC or ELPAR to determine if element is descendant/child of "TOTAL ASSETS".

I really only use an element's index when looping through elements of a dimension in a TI process or using DIMIX to determine if an element exists in the dim. You could use the element index in a time dimension to return prior/next although my preference would be to use attributes in that case.

Hope this helps and welcome to TM1.


Posts: 2508
Joined: Tue Feb 16, 2010 2:39 pm
OLAP Product: TM1, Palo
Version: Beginning of time thru 10.2
Excel Version: 2003-2007-2010-2013
Location: Atlanta, GA

Re: Is TM1 dimension index important?

Post by tomok » Wed Nov 29, 2017 1:29 pm

The dimension index number has absolutely nothing to do with the parent child relationship of elements. It is simply the order of the dimension element in a list when the dimension was saved. When you create and save a dimension in TM1 (unless you used an XDI worksheet), the index numbers are automatically assigned either 1) in the order the element was added, or 2) alphabetically. It may or may not be in a parent-child order. Best to just forget about the index number except when using the DIMIX function in a TI process. For a rule, always use ELPAR or ELISANC, or create your own index number and store it in an attribute and reference it with ATTRN.
Tom O'Kelley - Manager Finance Systems
American Tower

Wim Gielis
Posts: 1846
Joined: Mon Dec 29, 2008 6:26 pm
OLAP Product: TM1
Version: PAL 2.0
Excel Version: 2016
Location: Brussels, Belgium

Re: Is TM1 dimension index important?

Post by Wim Gielis » Wed Nov 29, 2017 5:12 pm

One area where the the index order is important, is when you expand a consolidation.
Then TM1 will show the immediate children based on the index.
One might want to change the index when this is important.
For example, Total Year has 12 children as the months. Then you don't want to have a random list of elements when you expand Total year in a view.
Best regards,

Wim Gielis

Excel Most Valuable Professional, 2011-2014 ==> 105 TM1 articles and a lot of custom code
Newest blog article: Looping over input files

Thurston Howell III
Posts: 29
Joined: Fri Mar 10, 2017 8:26 pm
OLAP Product: TM1
Version: TM1 10.2.2
Excel Version: 2016

Re: Is TM1 dimension index important?

Post by Thurston Howell III » Thu Dec 07, 2017 4:49 pm

It is absolutely important, just not for what you're looking to do.

The benefit of the index numbers is that every element, regardless of how of how often it appears in a dimension, will have one identifying index number, which is very helpful if you're writing TI processes that edit your dimension structure or test for existing elements.

Post Reply