Beautifully done Mr. RR, short and sweet but very much to the point and clear. Thank you for this one and all the other work you do to help we developers deliver power BI solutions!
This was so helpful. Thanks. I have some questions though. I would be happy if you help me clarifiy these: - From my understanding there are no way to create a dataset using dataflow on the powerbi service. I have to create it using powerbi desktop, then publish the report, right? - Let's say we don't have complicated ETL or PowerQuery steps. We are handling the EL-T on the data warehouse. PowerBI gets fed by the ready-to-use tables. Do you think it's still beneficial to use the Dataflows? - I'm also confused by the logic here. We are already doing a data preparation steps while creating the data warehouse. I'm sure everyone does. Then we use dataflows/datasets/incremental refreshs again in the powerbi service. So, it's like doing the same thing twice? Is this services provided by powerbi can be considered like a cloud data warehouse solution? Yet, MS already has Azure Data Warehouse. - I've been researching about DataWarehouses recently. Can we say this in-memory model powerbi service stores is an OLAP Cube?
Thank you so much for sharing these videos. I have just one question, about performance when multiple reports are using a single dataset as source, does this have impact on performance of the reports connected to that single dataset?
Very nice explanation, But I have question, Does this mean we can develop an end to end project DWH (Since we are able to do transformation) in power bi? Any insights from any one pls
So you can create a dataflow in the Power BI service, but can you also create a dataset in the service as well? I know when you publish a Power BI report from Desktop to the cloud, the visual layer and the dataset goes up to the cloud. But what if you want to create a dataset without a tool like Power BI Desktop?
at the moment the only way to create the Power BI dataset is using Power BI Desktop, not through web unfortunately. this might change however in the future
I really do not understand this. Can't I import a file (CSV - which I thought composes a dataset) into Power BI Desktop - and then it connects and then I can ""Transform data" - and then it loads Power Query and I can transform it. YET this is a "dataset", not a "dataflow" (which seem to only be available in Power BI Service). Wouldn't this portion be part of the ETL layer/process, before I load everything into Power BI Desktop by clicking on the "Close & Apply" button on the "Home" tab in Power Query? Thanks.
Hi. Power Query (no matter on the Power BI Desktop, or Power BI service as Power Query online) is just the transformation engine. If Power Query sends data to the x-Velocity in-memory engine of Power BI, then it is dataset. If it export it as CSV files in Azure data lake storage or in Dataverse, then it is dataflow. The Power Query can be online but still loads data into a dataset. In short; it doesn't matter where the Power Query is. It matters where the data gets stored.
@@ThePradeeppawar you should find what is the way to access to its data. either direct access to the database, or through API. then in Power BI you can use the same approach too.
Is it possible to use Dataflows in Powerapps or Powerautomate? Would be really nice to transform data in Dataflow and use it in this solutions. Another thing, why do we have to do it in live connection? That limitates so much, as example if I want to define my Clients table to be a shared and promoted dataset so everyone use the same client base I wouldnt be able to connect other sourses into it. So if I want to use the same client dataflow in a report that uses tables from sales and in other that uses tables from Marketing that wouldnt be possible. Is the same thing that happens when I want to use another datasets in usage metrics (connect for example Users Department or plant to see wich department is using it more) I'm not able to because of that restrictions.
If you want to use the result of the dataflow in Power Apps and Automate, then I suggest create Power Platform Dataflows, that way you can store the results into CDS which is easily accessible in those services. The ability to have multiple data sources over a live connection is also underway, and will be available hopefully until end of this year (more or less). then you can combine this data source with anything else you want.
@@RADACAD Great, thanks for the response. I see about the Power Automate flows, I tried doing that but it's not the same thing. The entities in CDS require the data to be alot more friendly and its really frustrating to create a dataflow there. Wouldnt be easier if we just could access the power BI dataflow tables directly from the app? without loading in the CDS? CDS also has all company involved and its alot more controlled than a simple dataset from a workspace in dataflow. If I want to just do a simple app or try something I would have to go to an approval process because as I see, we shoulnd be putting every dataflow in CDS. This is why lists in sharepoint are so popular, because you can try so many things without too many company policies involved. Unfortunately if you have to load everything in CDS you lose that and also get politics in the way to use the power Query online (dataflows) for simple datasets in power apps. Loading and transforming data in powerapps should be as easy as loading and transforming data in power BI dont you agree?
This was so, so useful!
I really appreciate this gentlemen's work, I listened to his video on Power Query M vs Dax, that was just perfect explanation. Thanks man
Beautifully done Mr. RR, short and sweet but very much to the point and clear. Thank you for this one and all the other work you do to help we developers deliver power BI solutions!
Thanks for your nice comment Jeff!
Great explanation! Thanks!
Fantastic explanation
Excellent explanation. Thank you.
Perfect explanation ! thank you
This was so helpful. Thanks. I have some questions though. I would be happy if you help me clarifiy these:
- From my understanding there are no way to create a dataset using dataflow on the powerbi service. I have to create it using powerbi desktop, then publish the report, right?
- Let's say we don't have complicated ETL or PowerQuery steps. We are handling the EL-T on the data warehouse. PowerBI gets fed by the ready-to-use tables. Do you think it's still beneficial to use the Dataflows?
- I'm also confused by the logic here. We are already doing a data preparation steps while creating the data warehouse. I'm sure everyone does. Then we use dataflows/datasets/incremental refreshs again in the powerbi service. So, it's like doing the same thing twice? Is this services provided by powerbi can be considered like a cloud data warehouse solution? Yet, MS already has Azure Data Warehouse.
- I've been researching about DataWarehouses recently. Can we say this in-memory model powerbi service stores is an OLAP Cube?
Up to the point. Thanks
great lecture ! thank you a lot!
Thank you so much for sharing these videos. I have just one question, about performance when multiple reports are using a single dataset as source, does this have impact on performance of the reports connected to that single dataset?
thanks
Great work !
how many pbi dataflow connections can we have from desktop at a time ?
we are connecting pbi dataset from get data ,where pbi dataset is prepared ?
Hello Master,
thanks for generating and sharing quality videos, please
What is the storage capacity of Data Flow?
Would it be the same as Workspace?
It stores data in Azure Data lake storage, normally it is part of the space you got in your license. But you can bring your own storage
Can we use two shared datasets in one report?
Very nice explanation, But I have question, Does this mean we can develop an end to end project DWH (Since we are able to do transformation) in power bi? Any insights from any one pls
MS will probably say that you can't, but you actually can and it's cheap
@@gulhermepereira249 correct
So you can create a dataflow in the Power BI service, but can you also create a dataset in the service as well? I know when you publish a Power BI report from Desktop to the cloud, the visual layer and the dataset goes up to the cloud. But what if you want to create a dataset without a tool like Power BI Desktop?
at the moment the only way to create the Power BI dataset is using Power BI Desktop, not through web unfortunately. this might change however in the future
I really do not understand this. Can't I import a file (CSV - which I thought composes a dataset) into Power BI Desktop - and then it connects and then I can ""Transform data" - and then it loads Power Query and I can transform it. YET this is a "dataset", not a "dataflow" (which seem to only be available in Power BI Service). Wouldn't this portion be part of the ETL layer/process, before I load everything into Power BI Desktop by clicking on the "Close & Apply" button on the "Home" tab in Power Query?
Thanks.
Hi.
Power Query (no matter on the Power BI Desktop, or Power BI service as Power Query online) is just the transformation engine. If Power Query sends data to the x-Velocity in-memory engine of Power BI, then it is dataset. If it export it as CSV files in Azure data lake storage or in Dataverse, then it is dataflow.
The Power Query can be online but still loads data into a dataset.
In short; it doesn't matter where the Power Query is. It matters where the data gets stored.
Hello sir, could you please show one example how to get the data from ServiceNow tool into Power bi desktop
what do you mean by ServiceNow?
@@RADACAD its a ticketing tool
@@ThePradeeppawar you should find what is the way to access to its data. either direct access to the database, or through API. then in Power BI you can use the same approach too.
@@RADACAD could you please make the video how to get data from Google sheets
Is it possible to use Dataflows in Powerapps or Powerautomate? Would be really nice to transform data in Dataflow and use it in this solutions.
Another thing, why do we have to do it in live connection? That limitates so much, as example if I want to define my Clients table to be a shared and promoted dataset so everyone use the same client base I wouldnt be able to connect other sourses into it. So if I want to use the same client dataflow in a report that uses tables from sales and in other that uses tables from Marketing that wouldnt be possible.
Is the same thing that happens when I want to use another datasets in usage metrics (connect for example Users Department or plant to see wich department is using it more) I'm not able to because of that restrictions.
If you want to use the result of the dataflow in Power Apps and Automate, then I suggest create Power Platform Dataflows, that way you can store the results into CDS which is easily accessible in those services.
The ability to have multiple data sources over a live connection is also underway, and will be available hopefully until end of this year (more or less). then you can combine this data source with anything else you want.
@@RADACAD Great, thanks for the response.
I see about the Power Automate flows, I tried doing that but it's not the same thing. The entities in CDS require the data to be alot more friendly and its really frustrating to create a dataflow there.
Wouldnt be easier if we just could access the power BI dataflow tables directly from the app? without loading in the CDS?
CDS also has all company involved and its alot more controlled than a simple dataset from a workspace in dataflow.
If I want to just do a simple app or try something I would have to go to an approval process because as I see, we shoulnd be putting every dataflow in CDS.
This is why lists in sharepoint are so popular, because you can try so many things without too many company policies involved.
Unfortunately if you have to load everything in CDS you lose that and also get politics in the way to use the power Query online (dataflows) for simple datasets in power apps.
Loading and transforming data in powerapps should be as easy as loading and transforming data in power BI dont you agree?