Forum Discussion
Unable to rename Gen2 Dataflow
- 2 years ago
The case # is 2311030040012138. Looks like whatever the issue was has been resolved. Gen 2 Dataflows we create now don't have issues. Some of the dataflows that were created a couple of weeks ago now though are completely toast. Ownership cannot be switched and the owner can't even open the dataflow. Oh the joys of pre-release software.
One of the things noticed when dataflows miraculously started working again was the appearance of a DataFlowsStagingLakehouse that no one on my team had seen before. Doesn't show up in the workspace but is listed as an option when Lakehouse is selected as a data destination.
Oops. Dataflow that was working now had all the Lakehouse destinations removed. What's going on today? Clearly something is being jacked with on the Power BI service. Other users on my team also cannot take ownership of Dataflows to modify or correct. Please fix ASAP or let us know what the deal is.
- Anonymous2 years agoNot applicable
Hi MartinMason ,
Thanks for using Fabric Community and reporting this.
Apologies for the issue you have been facing. I would like to check are you still facing this issue?
It's difficult to tell what could be the reason for this performance. I would request you to wait for sometime and try again.
If the issue still persists, can you please share few more details about the nature of the failure like screenshots? error? sessionID? repro steps?
I would be able to guide you better once you provide these details.