Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hello
I have this question, when to use dataflow & when to use dataset?
from my understanding dataset contains data+transformations for data +relationships+dax etc, so when i upload my model it becomes a dataset
for dataflow , difference is that i dont have model & dax in it , & transformations are done in powerquery in web
so when to use dataflow & when to use dataset?
in addition if i have a dataset, and i want to transform the data to add some columns etc, how to go back from dataset to the data if i am able to access the dataset, is there a way?
Thanks
Solved! Go to Solution.
@chahineatallah , dataflow is for a common set of tables that need transformations and needs to be used across various projects. Dataflow will become a source for the dataset. Dataflow is a set of tables but not model.
Dataset is a model with a Table , relationship, new columns, and measures. It is ready to be used report.
We can have all dimension tables and the small facts and static tables as dataflows and let all global team uses that without knowing what all needed to build those.
Say, for example, I have an article dimension that uses a few sources including excel. So I made a dataflow global dimenions with Article and few other dimensions.
Then I used that in Sales Dataset and Purchase Dataset and allowed sales and purchase team to use dataset to create report
Dataflows and Dataset Design Pattern implementation: https://youtu.be/zwhJ1hWPcrA
https://radacad.com/dataflow-vs-dataset-what-are-the-differences-of-these-two-power-bi-components
@chahineatallah , dataflow is for a common set of tables that need transformations and needs to be used across various projects. Dataflow will become a source for the dataset. Dataflow is a set of tables but not model.
Dataset is a model with a Table , relationship, new columns, and measures. It is ready to be used report.
We can have all dimension tables and the small facts and static tables as dataflows and let all global team uses that without knowing what all needed to build those.
Say, for example, I have an article dimension that uses a few sources including excel. So I made a dataflow global dimenions with Article and few other dimensions.
Then I used that in Sales Dataset and Purchase Dataset and allowed sales and purchase team to use dataset to create report
Dataflows and Dataset Design Pattern implementation: https://youtu.be/zwhJ1hWPcrA
https://radacad.com/dataflow-vs-dataset-what-are-the-differences-of-these-two-power-bi-components
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 51 | |
| 37 | |
| 35 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 72 | |
| 70 | |
| 39 | |
| 34 | |
| 23 |