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 Submitted
Workspace FTM Base
Created by Guest
Created on Mar 16, 2022

Storing of enriched/additional information outside of the standard data model

in DNB we have to save a lot of information outside of the out of the box FTM Data Model. The main strategies available out of the box are:

- use object values/id references --> this leads to a quick proliferation in key value objects which impact readability/maintainability and performance if overused.

- us the extension table format --> maintaining these extension table increases the amount of table joins necessary and they are complex to create and maintain. Changes over time lead to repeated scripts which add on to the previous one. In FTM CPP we are already at 55 scripts to be run to deploy the extension tables of the solution

- store in ISF which is expensive to retrieve/parse and store

DNB would like to ask for a better way to manage this information. One solution that could be available is DB2 purexml. It would provide the ability to use documents with relative ease of access without having to parse entire documents ( as per ISF ). For example and additional column type to the object values could be purexml.

Whatever is choosen it should be visible through the UI but still remain flexible and easy/quick to access.

IBM consultant Criostoir Hyde has been working on some ideas. This case is to be regarded as a feature request by DNB to support Criostoirs suggestions.

Needed By Yesterday (Let's go already!)