Need programmatic control over synchronization

The main purpose of synchronization is to avoid thread interference. At times when more than one thread try to access a shared resource, we need to continue to ensure that resource will be used by only one thread at a time. The process by which this is achieved is called synchronization.

Synchronization groups that allow the book author to pick and choose which widgets in the book will be synchronized with each other is in scope for the 2022 Planning Analytics roadmap.

We will introduce groups of widgets that can be synchronized first. Directionality of synchronization between widgets or groups of widgets will be an additional enhancement. Between sync groups and directionality it should be possible to build some of the functionality described in this idea.

Just seconding this idea as a top priority functionality for dashboards in PAW.

Like others have said, we need the ability to read the selection value from a Selector or Dimension that is driving the process. Once we have the ability to do this, we can use it in MDX e.g.
{GENERATE(
{StrToMember("[Period].[" + $VARIABLE + "]")},
{[Period].CurrentMember,
StrToMember("[Period].[" + [Period].CurrentMember.Name + " YTD]"),
[Period].CurrentMember.Parent,
[Period].CurrentMember.LAG(12)}
)}

Above would allow you to retrieve 2023/08, 2023/08 YTD, 2023, and 2022/08 assuming the variable contained 2023/08

Similarly, we would need the ability to assign the MDX to a dimension whether it be context, rows or columns. Linking to a subset is probably not ideal and trying to manually update the MDX driving the view may be too complicated for many.

Ideally the scope also needs to be considered in terms of book vs sheet.

Synchronization is very basic in PAW. We need more control over the objects in PAW dashboards. Simple requirements needed in any dashboards are not met by this tool and it's impacting the adoptability. Just to get variance on 2 dynamically selected versions, we ended up writing mdx statements with mdx cube and that's very very complex for a very simple requirement. It needs to have drill downs from one chart to another!

I suggest you try to use the Workbench area that is designed for Modelers. Many ideas that are suggested have been implemented ( default vie, search, etc) already and more on the way. Thank you for the great observations.

Very good suggestions! If IBM wants PAW to be used a reporting tool, it needs more flexibility and control..

I did enter the following in the additional information but it doesn't seem to show up so adding as a comment.

These are possible ways that better synchronisation could be achieved

1. The ability to draw lines between grids and selectors to specify exactly what should sync with what.

2. The ability to introduce names for selectors so that it is possible to specify which named selection a grid should sync with. Even if that name still has to be eg a Range Name on a Web Sheet that would be useful.

3. The ability to introduce new calculation capabilities so that the related member on the grid could be calculated, eg adding '_YTD' to the monthly Period would work for this scenario. However, there would also be other more complex scenarios, eg they select a sub group but want to derive the parent group and show a grid for that. At present calculated members can only be used for numeric calcs and cannot be used as selectors.