Forum Discussion
Dataflow Best Practices
Hi,
Anyone got a good article on DataDlows? I want to see info on following
- Naming conventions
- Version Control
- Dataflows that can be used globally and not spcific to one area of the business i.e. Createa Dataflow for Postcodes this can be used across the business as it is a common dimension, but would we create a a Global Workspace for these common Dataflows?
- Incremental Loads
Thanks
Hi there. Microsoft has some articles about some practices. I don't think they have answer for all your questions, but you can navigate through them to deep dive into dataflows.
- https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-best-practices
- https://docs.microsoft.com/en-us/power-query/dataflows/best-practices-reusing-dataflows
Naming conventions can replicate practices from azure. Like dfw-[name]. You can also start with licence in case you have premium and pro dataflows at different workspaces. I don't think there is something related to version control. That's something I have complained before and there is no planning. I would say get in the advanced editor, copy the code to a plain text file with ".pq" extension and store it in a repo. It's not a nice practice, but at least it's something to control the version of code.
I hope that helps,
1 Reply
Hi there. Microsoft has some articles about some practices. I don't think they have answer for all your questions, but you can navigate through them to deep dive into dataflows.
- https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-best-practices
- https://docs.microsoft.com/en-us/power-query/dataflows/best-practices-reusing-dataflows
Naming conventions can replicate practices from azure. Like dfw-[name]. You can also start with licence in case you have premium and pro dataflows at different workspaces. I don't think there is something related to version control. That's something I have complained before and there is no planning. I would say get in the advanced editor, copy the code to a plain text file with ".pq" extension and store it in a repo. It's not a nice practice, but at least it's something to control the version of code.
I hope that helps,