Self-Service ETL: The PowerBI Data Flows
summary
Live demo builds two data flows (Customer and Geography) then a merged CustomerGeo flow, using the portal Power Query editor and Power Query/M scripts moved out of PBIX into app workspaces. On‑prem SQL access requires the on‑premises gateway and gateway connections; linked entities normally need Premium but a practical workaround disables enable load so refresh runs. Lineage breaks for unloaded entities; storage sits on Azure Data Lake Storage Gen2 and the flows successfully refresh with the gateway.
AI-written summary · about
chapters (20)
- 0:00Introduction and setup
- 1:04About the speaker
- 2:07Power BI ETL problem
- 3:51Introducing data flows
- 4:33Data flow requirements
- 6:19Demo environment setup
- 7:42Configuring on-premise gateway
- 9:57Creating a workspace
- 10:40Building first data flow
- 15:42Migrating existing queries
- 19:47Linking data flows
- 25:05Premium account limitation
- 25:49Viewing data lineage
- 29:25Premium per user update
- 30:53Endorsement feature
- 33:42Using data flows in Power BI Desktop
- 35:58Key differences data sets vs flows
- 37:23Self-service ETL role
- 38:50Enterprise ETL vs self-service
- 39:31Summary and resources
related talks
48mGo With The (data)Flow
45mRebooting your SME Data Analysis Strategy
18mEmpowering Business Through Data
50mPower BI Incremental refresh made simple.
50mPower BI + Azure Synapse Analytics: Beginning your journey
52mPower BI + Azure Synapse Analytics. All you need to start creating a unified analytics solution
50mPower BI dataflows: building your own refresh orchestration
59mFinding Your Balance: BI in the Cloud, On Premises, or Both