Hi,
Unless I have misread what Dean wrote (which probably wasn't enough information to be sure of anything) he already appears to be using the methodology that Declan spelled out,
It would appear that Dean is saying the methodology outlined by Declan works for exploration views but not for graphs?
So I am wondering if this is a bug with graphs/visualisations. I too have had issues with graphs, though not tested this specific issue.
As for Paul's RFE, I suspect that could also be solved by using Declan's approach.
However, as Paul notes this is way too over-engineered and complicated. These requirements or similar ones are a recurring theme.
I also agree with Ryan and George's comments.
Hopefully the improvements to synchronisation that we would all like to see, and which have been raised in numerous RFE's and community posts, will be high up on IBM's agenda.
regards,
Mark
------------------------------
Mark Wragg
------------------------------
Original Message:
Sent: Wed October 20, 2021 04:49 PM
From: Dean Watts
Subject: Are Dynamic MDX Subsets allowed in PAW visualizations?
I'm working with PAW 63. I am using a selector cube for users to choose a cost center from a picklist and retain. I have an Explorer view that has an MDX subset on the rows which references that cell in the selector cube (STRTOMEMBER). I also have a line visualization where I use a similar subset also pointing to the same cell in the selector cube on the y-axis. When I select a new cost center from the picklist the Explorer view renders perfectly however I get an error message for the line chart that says the cost center is missing and chart does not render. However the error message refers to the previous cost center before the new one selected. When I go to the fields the y-axis box has the start of the error message in it. When I click the ellipsis and open the subset editor, the MDX is rendered and the correct cost center is there. I close the subset editor and the graph then renders correctly.
Has anyone else seen this behavior?
Dean
------------------------------
Dean Watts
------------------------------
#PlanningAnalyticswithWatson