Dataflow group

[rdnguyen]

Regarding the dataflow design, would you separate all staging Dataflow which connected datasource in another Workspace other than those you do transormation serving reporting purpose?

Kindly advise!

Best regards

Rich

[edhans · Accepted solution]

If you want to isolate dataflow developers from source systems for whatever reason (security, consistency of table design from various systems, etc) sure. 

I've seen some orgs keep all end user dataflows (for report/dataset devs in Power BI) in one workspace just for dataflows so they don't intermix with other workspace artifacts and aren't subject to org changes where workspaces may be renamed or even deleted. 

[v-yanjiang-msft · Accepted solution]

Hi @rdnguyen ,

If you have a set of dataflows that you use as staging dataflows, their only action is to extract data as-is from the source system. These dataflows can be reused in multiple other dataflows. 

If you build all your dataflows in one workspace, you're minimizing the reuse of your dataflows. You can have some generic workspaces for dataflows that are processing company-wide entities. You can also have some workspace for dataflows to process entities across multiple departments. And you can also have some workspaces for dataflows to be used only in specific departments.

Reference: Best practices for reusing dataflows across workspaces - Power Query | Microsoft Docs

Best Regards,
Community Support Team _ kalyj

If this post helps, then please considerAccept it as the solution to help the other members find it more quickly.

[edhans · Accepted solution]

If you want to isolate dataflow developers from source systems for whatever reason (security, consistency of table design from various systems, etc) sure. 

I've seen some orgs keep all end user dataflows (for report/dataset devs in Power BI) in one workspace just for dataflows so they don't intermix with other workspace artifacts and aren't subject to org changes where workspaces may be renamed or even deleted.