Hi James,
if my response to you came across as a bit irritable then I can only apologise.
I really appreciate that you took the time to test and respond!
I only wish I had emphasised this in my response to you!
I am not sure what you mean by "if I use subset editor in the filter and select the subset that was used in Excel"
To be clear, I am not synchronising a PAX sheet with any PAW objects, I am synchronising a PAX sheet with another PAX sheet, which are on different PAW tabs.
There are no PAW selections at all in the report, it is simply 2 PAX dynamic reports published in a PAW book.
Then I want to synchronise these 2 dynamic reports with each other.
Looking at what Ted Phillips said it appears that synchronisation doesn't work at the subset level, but the fact that it loses the subset seems like a bug to me.
Apologies if I have misunderstood anything
regards,
Mark
------------------------------
Mark Wragg
------------------------------
Original Message:
Sent: Thu May 27, 2021 04:06 AM
From: James McCarthy
Subject: PAX report subset issue in PAW when dimension is synchronised
What do you mean by this: As long as the correct subset is selected in the filter?
What I mean is, if I use subset editor in the filter and select the subset that was used in Excel (by selecting the set on the left and not the elements per below), the dropdown then gives me the elements from the subset:
From Subset Editor (Test Delete is my subset)
Published sheet:
i.e. the same elements. i.e. do you have the subset selected in the filter.
Why are you changing the subset in Excel as part of your testing? - This was not part of my test? It is all within PAW where the problem occurs, and there is no change in subset?
Just further checking the behaviour
The whole point is that I can synchronise between 2 different PAX reports published in one PAW book but on 2 different tabs. So the scope has to be the book.
Was just asking if it improved the behaviour. If you have something on another tab, it might be affecting the behaviour of the selection.
Maybe I'm missing the point here.
------------------------------
James McCarthy
Original Message:
Sent: Tue May 25, 2021 04:52 AM
From: Mark Wragg
Subject: PAX report subset issue in PAW when dimension is synchronised
Hi James,
thanks for the feedback.
What do you mean by this: As long as the correct subset is selected in the filter?
The subset is a subnm in a pax sheet and what appears in the filter are the elements in this subset and not the subset itself.
Why are you changing the subset in Excel as part of your testing? - This was not part of my test? It is all within PAW where the problem occurs, and there is no change in subset?
"Try changing the synchronisation to only being sheet rather than book specific"
The whole point is that I can synchronise between 2 different PAX reports published in one PAW book but on 2 different tabs. So the scope has to be the book.
regards,
Mark
------------------------------
Mark Wragg
Original Message:
Sent: Tue May 25, 2021 04:27 AM
From: James McCarthy
Subject: PAX report subset issue in PAW when dimension is synchronised
Just tried this myself and I think works OK. As long as the correct subset is selected in the filter.
Published with subset. Get members I expect.
Synchronise. Get members I expect.
Change the subset in Excel. Get members I expect in filter but not in published element.
Save book and re-open. Get members I expect in both.
That said, I have seen instances where behaviour has not been as expected. Try changing the synchronisation to only being sheet rather than book specific. Then also try doing the same thing on a fresh book. Feel like some corruption can occur sometimes and I find starting on a fresh book can help this. Is one of those difficult to replicate things which makes it tricky to raise as a PMR.
------------------------------
James McCarthy
Original Message:
Sent: Fri May 21, 2021 10:46 AM
From: Mark Wragg
Subject: PAX report subset issue in PAW when dimension is synchronised
Hi,
I have created a PAX dynamic report which is published in PAW.
There is a Subnm in the PAX report for version, as follows:
=SUBNM("Server:Version","PAW_Active Versions",1)
This should return members of the subset, PAW_Active Versions.
Within PAW I am synchronising the version dimension (it should be noted that if synchronisation is turned off the problem I describe below does not appear, therefore I am pretty confident this is caused by synchronisation).
When I first load the PAX sheet in PAW, in the version dropdown I see the correct elements, as per image below:
------------------------------
Mark Wragg
------------------------------
#PlanningAnalyticswithWatson