Remove Obsolete Source from Lineage View

[j_ocean]

When you create a dataflow, markers for connections outside the workspace appear in lineage view. If it later comes to be that this conneciton is no longer needed, deleting the table does NOT remove the marker in lineage view.

How do I remove it?

The only solution I found is to download/reupload the json, re-point all downstream resources, and delete the original. This is not practical in many cases. I've tried deleting the connection from within Power Query / Manage Connections, but this does not  work. There is no Gateway.

Dataflow-to-dataflow connections within the same workspace do keep up with this sort of change.

[Anonymous · Accepted solution]

Hi,@j_ocean 

Regarding the issue you raised, my solution is as follows:

First of all, you can change the part of the data source source you need to modify, Ctrl+select in PowerQuery, and click Copy to preview the data:
 

Then click EnterDate to paste the data and delete the query that references other data sources, so that your data comes from the parts you manually entered and not from other data sources:

Next, find the options and change the gateway to none:
 

Change the gateway used in a dataflow project - Power Query | Microsoft Learn

This way, there is no relational data source before the dataflow:

Of course, the limitation of this method is obvious: the data cannot be too large, and the data structure cannot be changed.

If you have any new ideas, you are welcome to contact us.
 

Best Regards,

Leroy Lu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi,@j_ocean 

Regarding the issue you raised, my solution is as follows:

1.First, here's what I created to simulate your needs:

2.Second, you can use the new query to replace the data source, but it should be noted that you need to keep the data structure the same as the original data, such as the query name, column name, and number of columns:

Of course, we recommend that you make changes to the data source in the advanced compiler:

3.Then upload it to the service and replace the original PBIX file, and the lineage chart will be changed:

Of course, if you have any new ideas, you are welcome to contact us.
 

Best Regards,

Leroy Lu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[j_ocean]

It appears from your final image vs the first that you simply refactored the system to be all in the pbix, which is not what I need. 

You started with 

SQL → Dataflow → Semantic Model → Report

I need 

Dataflow → Semantic Model → Report

Not 

SQL → Semantic Model → Report

[Anonymous · Accepted solution]

Hi,@j_ocean 

Regarding the issue you raised, my solution is as follows:

First of all, you can change the part of the data source source you need to modify, Ctrl+select in PowerQuery, and click Copy to preview the data:
 

Then click EnterDate to paste the data and delete the query that references other data sources, so that your data comes from the parts you manually entered and not from other data sources:

Next, find the options and change the gateway to none:
 

Change the gateway used in a dataflow project - Power Query | Microsoft Learn

This way, there is no relational data source before the dataflow:

Of course, the limitation of this method is obvious: the data cannot be too large, and the data structure cannot be changed.

If you have any new ideas, you are welcome to contact us.
 

Best Regards,

Leroy Lu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[j_ocean · Accepted solution]

For anyone reading this later, this did not solve the issue. MSFT accepted their own solution. 

I've given up and am enduring with the reupload-json method mentioned in the original post.