Reversing the hierrachy/order

[dima55]

Hi All

I am new to TM1 and recently encountered with a wierd problem.In hierarchy usually the parent element is at the top and the leaf level elements at bottom . I recently had to make changes to a element name and happen to open a dimension in which the leaf elements were at top aggreagating downwards to parent elemts. This created a lot of confusion
1. Is there a way to reverse this hierarchy
a.If yes, is there any impact(well i dont see any as the purpose would be same). If No could any one explain why we use reverse hirarchy.

I searched in manual alot but with no luck.

2.Also say we have parent element A with b ,c and d as its child . Does changing the order of b,c and d to any other order say c, b and d affect anything
Because somehow it happened such that in test i had the order as b , c and d in ascending ,in Prod i dont know how the order was chnaged to c , b and d
.i encounterd problem when i tried to change the order , even after saving it as b,c and d the order used to change back to c,b and d. then atlast i saw another parent which had A as its child and the order as c,b and d. So i had to change the order in both .My concern is

1. Does the order of siblings matter and if so if we have elements in another parent should we change both the order or did i miss anything and got lucky that i changed the order in another parent and the order of elemnts in the A parent changed by itself.

Thanks
Dima

[asutcliffe]

Do you just want to switch off View->Expand Above in the subset editor?

edit: typo

[dima55]

Thanks asutcliffe

But is there any diff when you use this feature. Does anything else in the dimension gets affected ?

Thanks
Dima

[tomok]

It doesn't actually change anything in the dimension. It's a client-only setting that is really nothing more than a sort-order toggle switch for the hierarchy tree.

[qml]

This parameter of a subset only changes how elements are displayed in that specific subset. It does not affect the actual order of elements in the dimension.

In most cases users don't even care what the dimension order is, because they always view elements through the subset layer. All you really need to do is define subsets for this dimension properly, including Default subsets (static or dynamic) so that they present the sort of hierarchy tree that users can understand and work with.

[dima55]

Thanks alot qml and tomok

Any Insights on this

We have parent element A with b ,c and d as its child . Does changing the order of b,c and d to any other order say c, b and d affect anything
Because somehow it happened such that in test i had the order as b , c and d in ascending ,in Prod i dont know how the order was chnaged to c , b and d
.i encounterd problem when i tried to change the order , even after saving it as b,c and d the order used to change back to c,b and d. then atlast i saw another parent which had A as its child and the order as c,b and d. So i had to change the order in both .My concern is

1. Does the order of siblings matter and if so if we have elements in another parent should we change both the order or did i miss anything and got lucky that i changed the order in another parent and the order of elemnts in the A parent changed by itself.
If No why i couldnt save the order with changing the order of same elements in another parent

Thanks
Dima

[declanr]

Thanks alot qml and tomok

Any Insights on this

We have parent element A with b ,c and d as its child . Does changing the order of b,c and d to any other order say c, b and d affect anything
Because somehow it happened such that in test i had the order as b , c and d in ascending ,in Prod i dont know how the order was chnaged to c , b and d
.i encounterd problem when i tried to change the order , even after saving it as b,c and d the order used to change back to c,b and d. then atlast i saw another parent which had A as its child and the order as c,b and d. So i had to change the order in both .My concern is

1. Does the order of siblings matter and if so if we have elements in another parent should we change both the order or did i miss anything and got lucky that i changed the order in another parent and the order of elemnts in the A parent changed by itself.
If No why i couldnt save the order with changing the order of same elements in another parent

Thanks
Dima

Ordering of children under a parent is pretty irrelevant, the only thing that matters is their component weighting for that parent.

If you want to sort the dimension in a specific way have a look at the DimensionSortOrder function within the manuals, you can run it from a TI and it will allow you to sort the dimension by hierarchy but then you can either sort children under a consolidation by the order in which they were inserted or alphabetically etc.

HTH

[Steve Rowe]

It's not impossible that you could have a rule that uses a Elcomp which has a positional reference to the child of a consolidation. The result of this would change if you changed the dimension structures.

It would be pretty unusual thing to do and in general its considered bad practice to use any functions in rules or TIs that reference the index of an element in a dimension. I think using Dimix for a membership test is about the only one that I use.

Cheers

[dima55]

Thanks alot declanr and Steve Rowe for your inputs.

Thanks
Dima