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
Created by Guest
Created on Aug 19, 2019

Support Temporal table(history table) in IDAA after it was loaded to IDAA as a regular table

Support Temporal table(history table)  in IDAA after it was loaded to IDAA as a regular table.

A regular table was loaded an use incremental update in the IDAA.

Later, this regular table was changed to HISTORY table.

We need that this table will continue support in the IDAA.

Today, because the type of the table was changed to 'H',  it dies not supported.


Please see our case TS002527283

  • Guest
    Aug 30, 2019

    The workaround is to remove the table from IDAA and add it back after the schema changes (activating or deactivating versioning) happen.