Please make it possible to open a dataflow gen2 without taking it over.
I wish we could open a dataflow gen2 even if it is "owned" by someone else in the workspace.
I think that the user who opens the dataflow gen2 should need to apply their own - or shared - data source connections in order to see any data in the query steps.
Otherwise, they would be able to use the owner's connections to interact with the data sources, and I don't think that's a good idea. Because the owner might not want other workspace members to use his/her connections. So I think that the user who opens the dataflow gen2 should need to apply their own - or shared - data source connections in order to see any data in the query steps.
I think it should be possible to open the item and start editing it, and not having to formally "take over" until you are ready to publish the changes.
Or some times you just want to open it for inspection without making any changes.
And if you do start to edit the dataflow, but then realize you aren't able to authenticate to all the data sources, then it should be possible to cancel so that the dataflow remains unchanged and the previous connections keep working.
Would be nice to have: before a user saves (publishes) changes to the dataflow, there could be a validation step to check that the user has authenticated properly to all of the item's data sources and data destinations, so that they won't cause the dataflow to stop working. If the validation fails, the dataflow should keep running with the previous connections and the changes should be undone.
11 Comments
- Joshua_RodgersNew Member
This is such basic and necessary functionality that has been requested since gen 1 dataflows. Please add it :)
- fbcideas_migusrNew Member
Please add this feature. It's such a PITA when it comes into data management -- we have many data scientists and data engineers who develop data procedures via dataflows, yet even Admin cannot view their works? Why.
- fbcideas_migusrNew Member
Please add this feature. It's such a PITA when it comes into data management -- we have many data scientists and data engineers who develop data procedures via dataflows, yet even Admin cannot view their works? Why.
- eric_isaacNew Member
The inability for team-members to view flows without wrangling a service account or manually importing the .json flows slows down development and limits knowledge transfer (both decreasing the chance that the organization will actually make the most effective use of Fabric that it could).
Pulled from my posting here:
https://community.fabric.microsoft.com/t5/Data-Engineering/Collaboration-in-Dataflows/m-p/4193592#M4344
- fbcideas_migusrNew MemberStatus added:Needs Votes
- ashukla4New MemberAbsolutely essential functionality.
- miguel
Community Admin
Status changed:Needs VotestoPlanned - KoenVerellenRegular VisitorThis would be so nice!
- miguel
Community Admin
Status changed:PlannedtoCompletedYou can currently view a Dataflow without taking it over in a read only mode
- acteon_jon_cattFrequent VisitorThis comment is inappropriate as it's misleading/incorrect - you still can't edit a Fabric Dataflow Gen2 that doesn't belong to you. 2026-07-27 "You cannot edit this dataflow because it is owned by another user. Consider leveraging the "Take over" feature from the Dataflow Settings page if you would like to take ownership."
Recent ideas
Add Automated Pre-Upgrade Compatibility Assessment for Fabric Spark Runtimes
Microsoft Fabric should provide an automated compatibility assessment before a workspace, Environment, notebook, or Spark Job Definition is upgraded to a newer Fabric Runtime. Spark runtime upgra...mourakshit9 minutes agoNew MemberNew1View0likes0CommentsSupport Creator-Independent Managed Identity and Ownership Transfer for Fabric Operations Agents
Microsoft Fabric Operations Agents should support an enterprise identity and ownership model that is independent of the individual user who originally created the agent. Today, an Operations Agent r...mourakshit10 minutes agoNew MemberNew2Views0likes0CommentsAdd Centralized Health, Freshness Monitoring, and Alerts for OneLake Shortcuts
Microsoft Fabric should provide a centralized health-monitoring experience for OneLake Shortcuts across workspaces and data sources. As organizations adopt OneLake Shortcuts at enterprise scale, hun...mourakshit13 minutes agoNew MemberNew2Views0likes0CommentsAdd Schema Compatibility Policies and Breaking-Change Detection to Fabric Event Schema Registry
Fabric Event Schema Registry should support configurable schema compatibility policies so teams can safely evolve event contracts without breaking downstream Eventstreams, Eventhouse ingestion, appli...mourakshit16 minutes agoNew MemberNew2Views0likes0CommentsAdd Dry-Run Simulation and Historical Event Replay for Fabric Activator Rules
Fabric Activator should provide a dry-run simulation mode that allows developers to test rules against historical or sample event data without executing real downstream actions. Activator rules can ...mourakshit17 minutes agoNew MemberNew2Views0likes0Comments