Hi @FrankPreusker , thanks for sharing this link. Wasn't easy but it ended up working for me at the end. I'll share my experience, hoping it can help others.
If like me your solution is 100% cloud based, you can skip to the very end of the page Frank refered to in his previous message because it's all for On-premises datasource... except for the "Purple Note" at the bottom on the page. I followed the instructions from that note and it worked ! Not easy I must say, but hey, better then nothing.
My case is a 4 year old dataflow that has a tone of old connections artefacts :
The current Query is has simple as it gets. It uses one connection to another dataflow from another PBI env. There's not trace anywhere of the connections you see in the lineage.
The instructions say : "To remove this connection, in the Power BI service, select the settings icon, go to Manage Connections and Gateways > Connections select the ellipsis menu by the connection name, then select Removeto remove the old/unused data source connection".
The challenge here is to figure out which connections are "old/unused", so you can safely delete. Because I'm the main developper of this solution since it started 4 years ago, I have a pretty good idea. But that screen had 38 connections listed and I can see how it could get daunting.
HINT! Something I discovered later. The little circular arrows under the Status column are buttons that allow you to check the connection status. And you can even get more details on the status by clicking on it after it displays. It not bullet proof method but I think it helps in the decision making regarding which connections you can safely delete.
I did all the deleting I thought was OK (I kept 10 of the 38, not bad for a 4year old clean up). Then I went back to the lineage view and it was all clean !
Note that I didn't even have to do this part of the instruction : "Then go to the Home page, select the workspace, select the dataflow to open it, and then in the Table name page, select Edit tables. Then in the Power Query editor, select Save & Close for the dataflows to be updated to the current data source connection and to remove the older connection."
Also note that the active datasource is not showing. I think that's because connections to another dataflow from another PBI workspace is current not supported in the lineage view... sounds weird right? Let me know if you know more about that last point.
Hope this can help someone.
Have a nice day,
--mo
@JenM , you're right, the problem is not resolved.
@v-kelly-msft , the workarounds you suggested don't address the issue at hand.
Here's my similar use case:
The Import from CDS dataflows has 2 entities from the same exact source (source A in the image below). The lineage shows an old artefact of a previously used connection that is no longer active in this dataflows. This is very confusing for the people responsible to maintain it!
When I go to Edit Entities, I can confirm via the Advanced Editor that both entitites are connected to source A.
I also tried to go to the Settings view of this dataflow and it gets worst there! There's a warning saying I can't refresh this dataflow because one of the credentials are invalid. Well, the invalid one is NOT used anymore. And to add to the confusion, there is also a 3rd source listed here which is neither used in that dataflow nor showing up in the lineage view.
I'm desperate to fix this and any help would be greatly appreciated!
Thank you.
Hi @JenM ,
Actually there's no such functionality to work it out,but I have a workaround,that is, you can click on the bottom right corner which I marked in red circle,then you will see that all related to the current datasource will be highlighted,and others will be grayed out.
Here is the related reference.
https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-data-lineage
Kelly
Hi @JenM ,
If so ,I have a simple way for you:
Connect the dateflow in desktop,then go to data source setting and clear your data source then reenter it:
Finally save as a new report or cover the previous report and publish to service.
I guess this way will help solve your issue.
Kelly
Helpful resources
Join us at the Microsoft Fabric Community Conference
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
We want your feedback!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Microsoft Fabric Community Conference 2025
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
A Year in Review - December 2024
Find out what content was popular in the Fabric community during 2024.
