Forum Discussion
Obsolete data sources in dataflow lineage
I have a dataflow with 8+ sources. Within this dataflow, over time I've moved from a development server to a production server, and I've referenced both dev and prod databases. I've also noticed...
I am having the same issue now. I am hoping Microsoft will fix this.
I tried the project options workaround mentioned in another comment, but it didn't work in my case.
The only thing that worked for me was exporting the dataflow as a json file and creating a new dataflow from the json, but creating a new dataflow will break downstream usage so I don't want to do that.