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.