I am pretty new to TM1, and one of the biggest issues I am struggling with is how to handle a hierarchy that isn't very clean. I have a consolidated level with values that are not unique. Are there any ways to handle this besides concatenating the values of the hierarchy together? To give perspective, I am using TM1 as a large OLAP Source of Data (Read Only).
Thank you in advance.
{Admin note: Moved to the correct forum.}
How to handle non unique values?
-
- Posts: 1
- Joined: Tue Jan 03, 2012 2:00 pm
- OLAP Product: TM1
- Version: 9.5
- Excel Version: Excel 2010
-
- MVP
- Posts: 1831
- Joined: Mon Dec 05, 2011 11:51 am
- OLAP Product: Cognos TM1
- Version: PA2.0 and most of the old ones
- Excel Version: All of em
- Location: Manchester, United Kingdom
- Contact:
Re: How to handle non unique values?
ComplexQry,
There are a few good explanations on consolidations shown in other threads on here if you search for them...
Your post doesn't really explain what it is you want:
In TM1 a leaf level element can exist under multiple consolidations (but it will add up into all of them)
If your leaf level element were say Product A and it can be sold by Shop 1&2... you would be looking at multiple dims as opposed to multiple hierarchies in 1 dim.
If you really do have 2 distinct elements with the same name then yes you will need to give them different names for the sake of TM1 to know which you are talking about.
There are a few good explanations on consolidations shown in other threads on here if you search for them...
Your post doesn't really explain what it is you want:
In TM1 a leaf level element can exist under multiple consolidations (but it will add up into all of them)
If your leaf level element were say Product A and it can be sold by Shop 1&2... you would be looking at multiple dims as opposed to multiple hierarchies in 1 dim.
If you really do have 2 distinct elements with the same name then yes you will need to give them different names for the sake of TM1 to know which you are talking about.
Declan Rodger