Right now, having multiple people edit dataflows is not just a pain, but risky. Assuming the person trying to take over a dataflow has access to all the sources, it's a serious click tax to have to rebind to a gateway every time (in an experience that's different from semantic models, btw). You have to edit the dataflow, find the menu to select the gateway (this experience is constantly changing too), know what gateway your data source is on (good luck with that) and save it to get the refresh back working and start editing.
But if you don't have access to the sources and happen to take over the dataflow, that refresh is now fubar until the old owner or someone else who does have access to all the sources can take it over and get it back bound to a gateway or authenticated to data sources. This is a real-world scenario that many teams in our company have experienced.
42 Comments
- We need to allow all admins of the workspace in which the dataflow is held to be able to edit the flow. Multiple people contribute to a dataflow at different stages of a project but all need to be able to review, understand and if necessary edit the dataflow
- Just a must have for team development, preferably like this: 1. Workspace Admins should have the same rights as the dataflow owner (Edit/ Settings/ Properties/ Refresh/ Export JSON/ Delete). 2. Members shall have read/write access only (Edit/ Export JSON). 3. Contributors shall be granted read access only (Can see all flows and their query steps (or M-code), but cannot change anything; may export JSON too) 4. Viewers shall have no access to dataflows
- Admins should be able to view, edit, etc. Viewers should be able to view code but not edit if using best practice of separate workspaces, should not be an issue as the only members should be involved in the development
- What if workspace owner same as dataflow owner.
We propose the ability for users other than the Dataflow Gen2 owner to collaborate on the same Dataflow Gen2.
We think this feature would be useful and would like you to improve the functionality.
- Status added:New
- Status changed:NewtoNeeds Votes
This is very basic functionality and has been asked for many times with gen1 dataflows. How are large enterprise customer supposed to manage dataflows when only 1 user can author them?
Hi, I hope that a such feature could be implemented as soon as possible. It could serve to some my customers. Thanks
This is really critical to enable the reliable use of dataflows on a larger scale. There are a lot of advantages to using dataflows but this lack of functionality really holds it back.
I think it would help for many use cases if there was a simple way to view an existing dataflow as read only - without having to take ownership straight away.
- Status added:Needs Votes
- Status changed:Needs VotestoNeeds Votes
This idea was merged with an idea from Power BI Dataflow Gen1 for the same task of co-authoring and being able to interact with the Dataflow (as either co-owner or simple members of the workspace)
