Hi Eric,
I might need a bit more detail to really understand this. However, what you are describing does sound like it's design intent. I'm making some assumptions here...
I'm assuming you are moving a hierarchy from the context (slice) position to the row or column position of the view. While in the slice position the hierarchy must have a single element selected, but you can optionally use a subset (public or private). If a subset is used then you can choose between elements in the subset while the hierarchy is in the slice position. If you move the hierarchy from the slice position to the row or column position then we will show all elements in the subset. If a subset is not used then we don't make any assumptions about what you want to look at. As you have already discovered, the real answer is to make use a subset with only the desired element. This could be a public subset that is defined by the TM1 modeler, it doesn't need to be private.
We could consider an enhancement that would show the default subset (subset named default if it exists) when a hierarchy is moved from the slice position to rows or columns. However, I suspect this would not be a good assumption for all Planning Analytics users.
Planning Analytics also supports unnamed subsets being used in the slice position of a view. This works the same way as a subset, but is not stored by the TM1 database (it's defined in either Excel or Workspace). In order to make an unnamed subset you must open the set editor and make a selection of elements, but not save the element back to the TM1 Server. The set editor will show 'Selection' on the right side pane. Assuming you make an unnamed set of only a few elements, then only those elements will be shown when moving the hierarchy position. The key here is the set editor MUST be opened. If you use the Keep and Remove functions directly in Excel sheet to define what elements you are looking at the selection will NOT be maintained when you move the hierarchy around. This is a limitation we want to tackle at some point in the future.
------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------
Original Message:
Sent: Fri December 13, 2019 09:01 AM
From: Eric M
Subject: PAX Swapping Dimension Between Context & Rows/Columns
Hello All,
When users swap these dimensions, ALL available members appear as default and it drags down performance. Sometimes or most times disconnects users amongst other things.
The only work around this is to first create a private subset for certain items. Then those selected members are actively available only after the swap.
Is this the way PAX supposed to work? And if so, Why? This isn't efficient when building ad-hoc reports.
Is there a better solution?
Cheers!
Eric
#PlanningAnalyticswithWatson