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 Not under consideration
Workspace Product Master
Created by Guest
Created on Oct 4, 2017

Entry preview does not consider local changes

"Entry preview" are using entry data as they are in DB and are not considering entry data client side as user may have updated some attribute values before launching entry preview.
As a result, user must SAVE entry before launching Entry Preview.
1) Edit an item in single-edit view
2) Update some attribute values
3) Launch an entry preview that display current item attribute values
=> entry preview shows item data as they are in DB and not as they are client-side.

Would it be possible to find a solution to manage this situation to avoid confusing between local/client-side update and DB2/server-side data ?
For example :
- trigger an item save automatically when user launch an entry preview
- check item was updated locally to stop entry preview / display popup error message "item was updated locally, please cancel or save prior to launch action"