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 Submitted
Workspace Planning Analytics
Created by Guest
Created on Sep 7, 2021

Pafe should always display what is in the cube when doing a retrieve.

If a cube cell evalutes to #N/A due to a divide by zero error or circular reference then the following behaviour is observed.

In an exploration view in PAW the cell value is #N/A, correct!

In quick and exploration reports then cell displays as empty, somewhat OK.

In custom and dynamic reports cell values display as 0, failure.

Pafe has a simple job, display the data in the cube, it shouldn't be interpreting the results and recasting them.

Not seeing #N/A values in the standard most common reporting formats introduces significant risks of issues with the underlying rules or structure not being obvious.

Additionally it breaks a use case that is in play extensively in a large clients legacy TM1 budgeting application where a rule is used to set cell values to =1/0, this is used to generate an input mask for the end users so they can see very clearly where data entry is expected.

Please reinstate the legacy behaviour of the legacy formula based reporting such that they display #N/A accurately reflecting what is in the cube.

Needed By Yesterday (Let's go already!)