Multiple authors for dataflows

[Jordan_Kline]

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. 

[Joshua_Rodgers]

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?

[fbcideas_migusr]

Hi, I hope that a such feature could be implemented as soon as possible. It could serve to some my customers. Thanks

[Derek4]

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.

[R_Dobler]

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.