For creating API pages/queries for Power BI pulling data from multiple sources, is it best to create a page for each table and pull them in, or is it better to combine them in one API query? Any guidance?
Kevin
For creating API pages/queries for Power BI pulling data from multiple sources, is it best to create a page for each table and pull them in, or is it better to combine them in one API query? Any guidance?
Kevin
Hi, I also tend to API, it has better performance than general WebService, it will be very helpful when dealing with large amounts of data.
Here is a great video about tips & tricks for Creating Custom APIs.
https://www.youtube.com/watch?v=5iRv0y0rVzw
Hope this helps.
Thanks.
ZHU
I'm a big fan of creating one api per fact/lookup table you require in Power BI.
The advantage is that these apis are then your building blocks you can reuse in other reports, and in Power BI Dataflows.
For the apis related to fact tables, you should also implement grouping/aggregating, to get the data at the level of granularity required in Power BI, not lower.
Then, also implement DataAccessIntent = ReadOnly, to get better performance.
In the apis you create, you can add other data items ofcourse, and in a query api, you can easily implement joins (inner, left-outer,...).
Sohail Ahmed
2,655
Mansi Soni
1,574
YUN ZHU
1,453
Super User 2025 Season 1