The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
We currently have data in our CRM system.
We need to bring this data into Power BI, either by retrieving it through the OData Source API or the Dataverse API, where the necessary joins are performed. Alternatively, the transformations can be carried out directly within Power Query.
We are working with multiple tables and a large dataset so which method is optimized one ?
The optimal approach depends on the size of your data and the complexity of the joining and transformation process. While it is influenced by your data structure, I prefer using Power Query because it offers flexibility, making it easier to handle future changes in the data structure.
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/dataverse-sql-query#limitations
As per this link , we can see that dataverse time limit is 5 minutes and its fixed , so what to do if timeout error happen ? Is there any fix available for this ?
EVERYTHING is easier when you use Power Query.
--Nate
What is driving your preference? Is it by ease of use, or by pure performance? While certainly not an expert on these two approaches, with both being API's, I bet the performance difference would be negligible. If you have to, develope a small test using both methods, same source table, same filters and number of rows returned, and time the results.
What method does your team prefer? What are they most comfortable with?
Proud to be a Super User! | |