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 Future consideration
Workspace Planning Analytics
Created by Guest
Created on Mar 3, 2021

Allow developers to set the column width for Cube views in PAW and disregard members as the context.

The general issue can be seen at this link

Currently if a developer creates a view in PAW and sets the length of a column, the width will persist if the members do not change.

However if the members change, is no longer there, the column widths do not persist, meaning the user will have to continually expand the column width, if they need to.

This is an issue particularly when you are using dynamic MDX to build subsets on the fly, for example if the subset references the logged on client.

We are finding that a solution to many issues in PAW revolves around using client attributes to return members in other dimensions.

Therefore, for many of our TM1 applications the client attributes cube is shown to the end user and it is currently not possible to make the column width persist because the member changes depending on the client who logged in. Assuming the client dimension is in the columns.

Needed by Date Apr 30, 2021
  • Admin
    Stuart King
    Mar 19, 2021

    Changed status to 'Under review'. This idea will be considered after the new Planning Analytics Workspace cube viewer widget is released. Current target for new cube viewer is Q3/Q4 2021.