Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
We've already implemented pulling data from Power BI Datasets using XMLA/ADOMD.
We fill a dataset and then serialize to Json.
Is there any reason to look at doing this via the new API vs. this method?
Thanks,
John
Hi @jprdynamicapps ,
The new DAX REST API avoids dependencies on Analysis Services client libraries, requires no connection to XMLA endpoints, and works in Power BI Premium as well as in Power BI shared capacity. In short, there are many good reasons for BI solution developers to evaluate this REST API during the public preview period.
There is a limit of 100,000 rows on this API.OLAP models are built for aggregation type queries, not large volume granular queries which are more suited for relational databases.
Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks, Liang.
I definitely understand why it's attractive. Just wondering if we should switch our current implementation. Should performance be any different?
Thanks.
John
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |