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,
Post an idea
Upvote ideas that matter most to you
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.
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.
Do not place IBM confidential, company confidential, or personal information into any field.