Forum Discussion
Connector Power BI dataflows (Legacy) vs Dataflows
Alright, after a lot of trial and error, we found out that we CAN have two datasources both using the new connector "Dataflows", one datasources connecting to Power Platform dataflows and the other connecting to Power BI Service dataflows, and at the same time.
The trick turned out to be to remove all original datasources involving dataflows everywhere (what a chase it was…), and recreate a lot of the dataflows from scratch again. I have to say that it is really diffcult (if possible) to comprehend what needs to be recreated and why. It seems as if some references to old datasources cannot be removed without a complete recreate of the dataflow in the following way (talking about Power BI dataflows now):
- Copy all queries from org. dataflow
- Create new dataflow
- Add a new query based on a datasource with the new Dataflow connector
- Then paste in the queries from the original dataflow
Spent 3 days!
Anonymous
Did you ever get a resolve to this.
I have Dataflows set up that all flow into a workspace called Shared Tables (We have a premium capacity) for Date and Time Tables, so that developers can just use these (we have Finance, Long and Short Form tables depedning on usage) and any changes are made once.
I have also built dataflows for source systems, for the same reasons. We have data from API's as well as Dataverse and some of our CRM and ERP systems.
Am I reading this right, that I am going to have to rebuild all of these and then let people know that they will have to chnage data sources. Not a problem, but obviously time consuming. . .
I get that this is an old post, but some of the other (Legacy) Dataflows have now gone, and I have seen the new Dynamics 365 (dataverse) connector.
Any further reading or updates v-zhangti would be really appreciated, as it could be that we need to rework a lot of our source data.
Thanks