Page 1 of 1
How to handle non unique values?
Posted: Tue Jan 03, 2012 2:13 pm
by ComplexQry
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.}
Re: How to handle non unique values?
Posted: Tue Jan 03, 2012 5:41 pm
by declanr
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.