Question & Answer
Question
Open the view with named subset after collapse the consolidation then expand it shows all members, which include eliminated member.
Is this an expected behavior?
Answer
This is the way TM1 has always worked.
Therefore, right now, when you modify the subset by collapsing or expanding a node, the client is creating a completely new subset (unnamed subset) with no memory of the previous one ( therefore 'breaking' the structure defined by the original subset definition).
Because of that when you then re-expand the node, it goes back to default behavior and you see all of the node's children in alphabetical order.
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCTEW","label":"IBM Planning Analytics Local"},"ARM Category":[{"code":"a8m50000000KzJsAAK","label":"Modelling-\u003EReporting (miscellaneous, non-specific)"}],"ARM Case Number":"TS008197918","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
24 January 2022
UID
ibm16550756