TM1 Forum

Morning folks,

This one has bothered me for long time and I'd like to see if anyone has the same problem and/or a workaround.

Most times after adding an existing node into a new consolidation, the node does not appear automatically in the consolidation. The node is infact in the consolidation but requires contracting and re-expanding the consolidation before it is visible in the subset editor.

For example, starting with: Add A to existing_rollup:
DimensionElementComponentAdd( 'Dimension', 'existing_rollup', 'existing_element_A', -1);

However, the subset editor will still only show: The existing_rollup has to be manually expanded and contracted (+'s) before it will behave as expected. The dimension is set for auto hierarchy sort order.

Ideas?

-- John

I'm guessing this is just something to do with the default subset you have saved. If you removed your default subset or you set it to only display the highest you should find your problem removed.

The description of your scenario is not clear. Are you saying you have:
1. The subset editor open looking at the consolidation before the process runs that adds children?
2. You open a subset after running the process and still need to contract/expand the parent to see the new children?
3. After running the process to add children and then after hitting show all in the subset editor you don't see all children under the parent?

Either way under each of these scenarios I would say that is pretty normal and expected behaviour.
1. how is the subset editor GUI supposed to know a process has been run and to automatically refresh? (It is showing a SUBSET which is nothing more than a LIST of elements which could be at any level, how is the GUI supposed to know that you want to expand a given parent to show all children?)
2. See answer to 1. A subset is a list of elements nothing more. It doesn't update just because dimension structure has updated (unless some members of the list no longer exist). If you need this to hapen then you have to use a dynamic subse not a static subset
3. Depending on the sort order of the dimension this could still be normal and expected behaviour as children will only show directly under their parents if their index order is defined before the next element with index that does not roll up to that parent. If you click on "sort by hierarchy" after "show all" do you then see the new children under the parent.

I don't think you have a problem or that there even is a problem from what you have described.

First, thanks for the quick responses.

lotsaram wrote:The description of your scenario is not clear. Are you saying you have:
1. The subset editor open looking at the consolidation before the process runs that adds children?
2. You open a subset after runnign the process and still need to contract/expand the parent to see the new children?
3. After running the process to add children ynd then after hitting show all in the subset editor you don't see all children under the parent?

#1 & #2: Nope and wouldn't expect it per your analysis
#3 : Yes. Even after a show all, I do not see the the child listed. After a Show All + Hierachy Sort, the children appear (same as with re-expanding/contracting as stated earlier).

The "logic" you describe is likely the culprit:

"...expected behaviour as children will only show directly under their parents if their index order is defined before the next element with index that does not roll up to that parent.

To me, this is not logical or expected behavior. If I have a dimension set for hierarchial sort, and I do a show all, why should I have to click Hierachry Sort inorder to see children in hierarchies regardless of their index order?

-- John