Cannot take over Dataflow Gen2 anymore

[Timal]

Hey,

Since today i'm having troubles taking over Dataflows. Worked fine previously for some reason it doesn't work today.

The error message is little helpful so maybe somebody has a clue whats happening here.

I'm using an Account with Fabric and Workspace Admin, so shouldn't be permission issue.

I'm trying to test the if the issue persists on other dataflows but currently i don't have another person/user to create a dataflow for me to take over. If i managed to organize a scenario i'll add it to the post.

Edit: Tested with another user, that person also cannot takeover any dataflows from me.

Thanks,

Tim

[Anonymous · Accepted solution]

Hi @Timal ,

Hi @naanii ,

This is a known issue that you can track on below document:

Known issue - Dataflow Gen2 ownership takeover fails - Microsoft Fabric | Microsoft Learn

Best Regards,
Adamk Kong

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

[NandanHegde]

MSFT is working on fixing this issue but for now below would be the workaround :

the way to re-recreate a Dataflow is the one mentioned in the article below through the usage of Power Query templates:

Power Query template (preview) - Power Query | Microsoft Learn

However, if you don't have a way to export that template because the person who owned the Dataflow is no longer able to export it (for whatever reason that may be), you could go into the .json to find the Mashup Document (the pure M script) and recreate your Dataflow manually using that .json.

[TBNPieter]

Hi Tim,

We are experiencing the same issue since the 3rd of july (West-Europe server). We are on a fabric trial at the moment and can't take over any dataflows gen2 made by another user (all Admins).

Please keep us informed if you or someone else finds a solution? 

[Timal]

Hey,

I've opened a Ticket at Microsoft and the confirmed, that this is a bug on their end for many customers. I haven't gotten the go for the bug being fixed yet but at least they told me that it's not our fault.

Hope this helps.

Workaround would be to download the JSON of the Dataflow (works without Owner), copy the M-Script and Create a new Dataflow. However in a Production Scenario, this is not feasible.

Regards,

Tim

[ramonsuarez]

@JFTxJ  Did you get a reply or find a workaround? 

[JFTxJ]

It looks like MS will be fixing this issue this week.  Here is the official response I got from support:

"We have checked this issue with our product group, they have confirmed that we have ongoing known issue, they also confirmed that, in this week the bugs will be fixed.

We request you to monitor the behavior for this week, please let us know, if you have any questions, we will be happy to assist you."

This response was received Monday July 8th.

So we will all be testing it every morning until it works!  lol

Cheers to all my Fabric friends!

[JFTxJ]

No progres on the issue this morning.  Same error.  I will keep you alll updated as soon as I hear from support.

[JFTxJ]

I can confirm that as-of this morning, this issue is now resolved for me (Canada Central region).

All my users are able to take over other's GEN2 Dataflows!

[MikeHasAProblem]

I too am experiencing this issue.

[JFTxJ]

I am experiencing the exact same issue since Wednesday last week.  Following.

I opened a support ticket with MS (2407020040005191)