TM1 Forum

Hi All,

I have a TI proc that uses DimensionElementComponentAdd and DimensionElementInsert to build a hierarchy of new elements.

The problem i have is the same code builds the dimension differently depending on what dimension it is built against, i set up a new dimension to test it and it builds the dimension how i want it to but when i run the code against the dimension it needs to be using it builds it slightly differently.

Im at a complete loss as to why, it's only one element that gets put in the wrong place and comparing the two dimensions i see the element has a different index order

example:

i have a C element and need to add two C elements and an N element as children:

in my test dimension it creates it like this:

C-
N 1
C 2
C 3

in my destination dimension it builds it like this:

C-
C 1
C 2
N 3

even though the code is the same.

If i try and move the N element up to where it should be and save it the element moves back down to the bottom the next time you sort it by hierarchy so im quite simply baffled and don't know where to start.

Has anyone ever experienced this in TM1, if so what was the cause/workaround?

Cheers

Hello,

Have you checked the properties of the test and target dimensions in the }DimensionProperties cube?

Regards,

Peter

Peter,

Spot on! Was not even aware of that cube and it had all 4 sort options set

SORTELEMENTSTYPE
SORTCOMPONENTSTYPE
SORTELEMENTSSENSE
SORTCOMPONENTSSENSE

Despite the fact that the user guide states that SortComponentsSense and SortComponentsType are not currently used?? not sure why we had those set but removing all the values has sorted the issue.

Thanks Very Much!