IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Add a new idea Subscribe
Status Delivered
Workspace Data Lineage by Manta
Created by Guest
Created on Sep 19, 2024

RELATED IDEAS

Lineage from SAS-grid should be able to export into Alation with correct representation

Background:

SAS files are being scanned from SAS-grid (local file system or git location) and Manta is able to analyse those files to create required lineages in Manta. 

Now, when we try to export the lineage to Alation we are not able to get any.

Process followed:

1. (This did not work). We created one BI server for SAS in Alation, configure the source id in Manta configuration and executed the export workflow successfully. However, no lineage is being integrated into Alation. 

2. (We get incomplete and incorrect lineage with this) We work with IBM team to solve this in working sessions and during one of them, the export configuration is modified (config related to DB2 is removed) and data flow server is restarted. After this lineage from Manta is visible in Alation but only for DB2 related lineages. 

Actual behaviour:

1. Lineage in Manta and Alation is not identical. 

2. We can see loops in Alation - source is pointing to some dataflow and instead of pointing to a target it points back to the source itself. After our discussion with IBM team, we got to know that this might be due to the fact that Manta is not able to export source and target properly to Alation and that is why Alation is completing those transformations as a loop.

Expected behaviour:

1. We expect to export Manta lineages into Alation without the need to depend on the workaround. 

2. We expect not to see any loops in the lineage representation of Alation. 

3. Also, in the official SAS lineage export to Alation is marked as "not supported" and we would like to see that changed. 

 

Screenshot 2024...
Screenshot 2024-09-19 at 7.45.47 PM.png
Open full size
Screenshot 2024-09-19 at 7.45.47 PM.png
Needed By Month
  • Admin
    Jakub Moravec
    Sep 4, 2025

    Subsequent changes will be tracked and delivered under Idea DATALIN-I-169

    Reply
  • Guest
    Sep 3, 2025

    Not delivered as expected in 42.13

    Reply
  • Guest
    Apr 15, 2025

    Sounds good.

    Update from some testing from my team.

    Even if SAS datasets are created manually in Alation (via VDS, or native/ocf dataset API), Manta still cannot link lineage into Alation because there is no screen in Manta where the Alation SAS Datasource ID is supposed to be configured.

    Devayon

    Reply
  • Admin
    Jakub Moravec
    Apr 11, 2025

    Hi Devayon,

    as per our follow up via email, we need to make code changes to support the export of SAS tables, currently we are targeting 42.13.

    To validate the objective, the team will make changes so that we start exporting Table/Synonym/View (and their columns) under the following hierarchy:

    • SAS Program

      • SAS Library

        • Table/Synonym/View

          • Column

    Best Regards,
    Jakub Moravec

    Reply
  • Guest
    Apr 8, 2025

    Update on my conversation with Jakub.

    1. Given that Manta scans SAS code and not SAS platform, Manta shouldnt create SAS tables in Alation, since that would be misrepreenting reality.

    2. However, Manta should publish lineage to Alation even if those objects are not yet scanned in Alation or not supported in Alation. This can be either as TMP objects (which alation deleted every ~30 days) or as EXT objects. Jakub has suggested that a Manta config change or code change may be needed to enable Manta to export SAS tables to Alation as TMP tables. He will get back to me with details.

     

    Devayon.

    Reply
  • Guest
    Feb 11, 2025

    Hi Jakub:

    Did you get a change to check the email from Devayon? If yes, please provide us the path that team should follow to export SAS lineage to Alation. 

    Reply
  • Guest
    Jan 28, 2025

    Hi Jakub, 

    I have responsed to you on Dec 16, 2024.

    Thanks, Dev

    Reply
  • Admin
    Jakub Moravec
    Oct 25, 2024

    Hello,

    a document outlining several options has been shared with     Devayon Das at Truist via email on October 10th, we are currently waiting for response, we need to clarify what approach would be ideal for Truist.

    Best Regards, Jakub Moravec

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.