Hi Stuart,
It would appear that Passed Context (something I wasn't aware of) is switched on by default when deploying applications, which is a shame.
Also, it is a shame there isn't the option to switch this on and off at the application level. It appears I will have to switch it off at the section level of the application.
Having said that this is way better than having to recreate all the applications from scratch, so much appreciated, I think this will solve the issue.
regards,
Mark
------------------------------
Mark Wragg
------------------------------
Original Message:
Sent: Wed May 28, 2025 09:42 AM
From: STUART KING
Subject: PAW version Application Issues
Hi Mark,
You can disable the 'context passing' feature in Applications. Please see: https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=applications-pass-context-between-books-in-application
Context passing uses the existing synchronization groups in Workspace books. Synchronization groups need to have the same name in multiple books for context passing to work. Besides disabling context passing you could also rename the synchronization groups in one of the books to prevent synchronization.
Let me know if this details helps.
------------------------------
Stuart King
Product Manager
IBM Planning Analytics
Original Message:
Sent: Tue May 27, 2025 10:54 AM
From: Mark Wragg
Subject: PAW version Application Issues
Hi,
we created a number of applications in an older version of PAW.
This version was one where if you opened a report from within the application it would not replace any books that were already open, but would instead open multiple books.
We used lifecycle manager to move these applications and the books to a server where version PAW 2.0.99 is deployed.
And in these later PAW versions when you open a book inside an application it replaces the book, so you only have one book open at a time. Which is fine by me.
However, we have seen an issue where it would appear that synchronisation passes between books inside the same application and the subsets of the report disappear (probably the result of the synchronisation issue).
This is causing real issues, because it basically destroys the subsets of the books, making them not fit for purpose.
For example, a book has employee subset where user can select a single employee or the "All Employees" consolidation.
But when the book is opened inside the application you only get to select individual employees, as the subset which includes the "All Employees" consolidation is no longer referenced in the book.
The same book works fine when opened directly from Report and Analysis, rather than from inside the application.
I have raised this issue with IBM support but was wondering if anyone else had experienced this issue?
I also wanted to make the point that IBM really need to up their game when testing these releases as it continually causes headaches for us.
And these are not minor issues.
yours frustratedly,
Mark
------------------------------
Mark Wragg
------------------------------