Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps (http://ibm.biz/Data-and-AI-Roadmaps) - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at https://hybridcloudunit-internal.ideas.aha.io/


Workspace Planning Analytics
Created by Guest
Created on Oct 19, 2021

Need programmatic control over synchronization

I tried to built a report in PAW which has three separate grids, showing Month, YTD and Full Year. These must be separate grids as the other things that the grids show are different. There is a selector at the top allowing the user to choose the month. What is shown in the Month, YTD, and Full Year Grid then needs to change according to the month.

This is a very common requirement, but is incredibly difficult to achieve in PAW. This should be made a lot easier.

I tried to do this using a web sheet using formula to derive the YTD and Full Year according to the selected Month. However, Synchronisation in PAW is not granular enough and any attempt to turn on Sync resulted in the SUBNMs on the Web sheet being corrupted eg the Month SUBNM got set to a Year. I tried arranging things so that the Month, YTD and Year all came from different Named Hierarchies but the Month SUBNM was still getting corrupted with a year.

The only option that appears to work is to use a SUBNM on a web sheet to let the user select the month and to then DBS this into a cube dimensioned by }Clients and Measures, and to derive the YTD and Full Year in Rules and then reference that in MDX subsets, which are then used in the YTD and Full Year Grids. This is far too complex a solution to a common problem

It should be possible to achieve this without using Web Sheets.


Needed By Yesterday (Let's go already!)
  • Guest
    Jun 22, 2022

    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.

  • Admin
    Stuart King
    Feb 28, 2022

    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.

  • Guest
    Feb 28, 2022

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

  • Guest
    Oct 28, 2021

    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.


  • Guest
    Oct 25, 2021

    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!

  • Guest
    Oct 22, 2021

    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.

  • Guest
    Oct 21, 2021

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


  • Guest
    Oct 21, 2021

    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.