Forum Discussion
Collaboration in Dataflows?
Does anyone here have advice (from documentation or from experience) for working with dataflows as part of a dev team?
Ideally, we'd like for more than one person to familiarize themselves with how a dataflow is working. To my understanding, each person would have to take-over the dataflow before being able to see the logic. We'd also like to track changes somehow, but didn't see a straightforward way to do so for dataflows.
For this reason, we've tried favoring notebooks, but the dataflows work really well for coworkers who aren't developers (e.g. tech-minded analysts). We are trying to figure out what options we have to make working with them a bit smoother. Any tips/tricks or features/plans I may not know about would help! Of course, if I'm misunderstanding the intended use/workflow for dataflows, knowing that would help too!
Please vote for this Idea to highlight the need:
Open Dataflow Gen2 without take over
https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=b3c9448a-5053-ef11-b4ac-00224853e085
7 Replies
- lbendlinSuper User
You are spot on. The need to "take over" is one of the biggest issues with dataflows.
- AnonymousNot applicable
Hi Anonymous ,
Thanks for the reply from lbendlin .
To collaborate in dataflow, you can share your workspace with your team members by adding them as roles in your workspace.
This way your team members can all access and collaborate on the data flow, and can all see and work on the same data flow without having to take over.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!- AnonymousNot applicable
For the benefit of anyone referencing this post at a future time - this does not appear to be how it works as of today. Clicking to see a DataflowGen2 prompts you to take-over the flow in order to interact with it. If there is another way to view it, I have not found it in the UI or the documentation.
The prompt:
ā
- lbendlinSuper User
One thing you can do to mitigate that issue is to regularly export the .JSON and push that into your github repo.