Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
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
Solved! Go to 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.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingHi @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.
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.
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.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingCovering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.