Forum Discussion
Cannot take over Dataflow Gen2
Perhaps this is a similar case:
The solution seems to be to export .json, and then open the .json in Notepad (or another tool), then copy each M code from the .json file and paste the M code into blank query (advanced editor) in a new Dataflow Gen2.
---
Maybe an alternative approach:
I haven't tried this, but maybe it's also possible to create a dataflow gen1 from the .json file (import json), and then export the dataflow gen1 as a power query template, and then import the power query template in a dataflow gen2.
Dataflow Gen2 (export json) -> new Dataflow gen1 (import json) -> Dataflow gen1 (export power query template) -> new Dataflow Gen2 (import power query template).
If that is possible.
Otherwise just export json from the original Dataflow gen2 and open the json in Notepad and copy the M code into a blank query in a new Dataflow gen2, as mentioned above.
Hi!
This is a known issue that you can track on:
Known issue - Dataflow Gen2 ownership takeover fails - Microsoft Fabric | Microsoft Learn
The workarounds shared by frithjof_v are valid.
Hi!
This is a known issue that you can track on:
Known issue - Dataflow Gen2 ownership takeover fails - Microsoft Fabric | Microsoft Learn
The workarounds shared by frithjof_v are valid.
miguel, I'm glad there's at least a semblance of a workaround, but do we have any kind of timeline on a fix from Microsoft? If a user owned multiple dataflows and leaves the org, those dataflows could be tied into numerous pipelines, so importing a new one is NOT ideal as this would also impact all data pipelines.
