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 Aug 8, 2019

Lineage Filter for Extension Mappings

When creating data lineage maps in IGC, it often gets too complicated or nested to track back to source column. When defining individual mappings, we would like to classify them as a computational or conditional dependency so that it is easier for the user to understand the type of dependancy in a specific data flow. 

To achieve this, we added a custom attribute to the Extension Mapping document. Though this data is available when the lineage is drawn out using an EMD, we would also want to be able to filter out specific extension mappings based on this kind of dependency. Ideally, if the user is able to hide out conditional dependencies and view just the computational dependancy, the lineage map becomes much more clear and powerful.


In the current version of InfoSphere, we are unable to create Lineage filters with 'Extension Mapping' as an asset type. While it is available as a condition under 'Extension Mapping Documents', it can only be used to hide the whole EMD rather than individual mappings.


This is an enhancement that would help make the lineage more user friendly and it will bee very useful to users across different domains.

Needed by Date Sep 30, 2019
  • Guest
    Aug 13, 2019

    Thanks for your suggestion. We will evaluate how Lineage Filters could support Extension Mapping in the future, as we develop a new user experience for the display and management of Lineage. We are also evaluating a new Business Lineage to address issues of consumability of Lineage for a general user. I understand the current limitation that does not allow such conditions on "Mappings" to be set and something we would evaluate -