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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Under review
Workspace Planning Analytics
Created by Guest
Created on Jul 13, 2021

PAW - Subset behavior

PAW can only refer to an element name of a subset and not to index .

If in a paw book we use a named subset that presents the current month , for example MAR from a subset that contains MAR FEB JAN

if the next month we update the subset with APR,MAR,FEB,JAN, PAW books stills open on MAR when it should open on the first element of the subset: APR.

If we use MDX subset based on cube values, it can works but with some dowsides. A major one is it display error pop-up in PAW view if MDX is empty. It would be great to be able to desactivate these pop-up (user parameter for example will be esmpty first time they connect).

Needed By Yesterday (Let's go already!)
  • Guest
    May 3, 2022

    Responding with a late comment, but perhaps this is useful.
    on the first point about managing the member that is shown from a subset - the most common approach I see for this use case is to utilize a lookup. By lookup I mean specifying in an MDX expression to show a lookup from a "Global Settings" cube where many Finance cycle members (ex: Current Year, Current Month, Forecast Start Month) are maintained for the model. This would avoid an empty subset result. This would also avoid a dependence on Index which in my opinion is not best practice since indexing is not always tightly controlled.

  • Guest
    Nov 5, 2021

    Hello Stuart,

    Thanks for your reply. I don't hink it is the right place for feed back answer because the lack of visibility.

    Anyway I understand your point, it can be very confortable to not change a default value all the time. However there is many cases where it is. Typically changing month or budget phase in financial application is the same requirement in pretty much all application as explained in PA community here.

    We manage to have a workaround by saving books with an out of scope element but it means to create or keep dummy members for each book modifications...

    A second linked subject is error popup. We really like to be able to desactivate them. We have some cases where we want a blank selection, for example when it is a salary selection (pretty impossible to put any default value here). That is not only anoying but really confusing for users. They think something wrong happend or the tool is broken... I have the feeling it would not be hard to add an option to desactivate them.

    Best Regards,

  • Admin
    Stuart King
    Sep 9, 2021

    I can reproduce the behaviour described in the description. However, I'm not sure if this is something we want to change. The view in Workspace remembers which subset is used for each hierarchy on the title axis of the view. It also tracks the currently selected member in the WHERE clause of the MDX statement for each hierarchy on the title axis. I expect the natural expectation for many uses cases to be the member remains the same, when possible, even if the members in the set has changed. We might consider how member context could be passed to views through synchronization functionality.

    I've set this idea to under review while we do additional investigation. Additional comments about the use cases that require the member to change based on index might help.