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 Not under consideration
Created by Guest
Created on Oct 22, 2021

Informatica lineage parsing beyond limitation(5 layers) in WKC

Customer couldn't see the column name under the transformation in lineage. and created PMR TS006637652

Got the following feedback :

The Open IGC bridge does not support feature level lineage. There is transformation level only lineage. This is related to an IIS limitation and as such there could only be a folder hierarchy of 5. So we use the "*" to depict all features that are nested below the 5th level of folder hierarchy.

This is specific to the nested "depth" of the bundle tree. We recommend, if possible, avoid nesting your bundle classes beyond five (5) levels. Everything works great, in all cases tested thus far for lineage, when the tree is five levels or less.

Almost all of the mappings are beyond 5 layers for the customer. Could you please remove the limitation

and allow unlimited layer parsing.

Best Regards,


Needed By Week