Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
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
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
8 | |
6 | |
5 | |
2 | |
2 |
User | Count |
---|---|
4 | |
4 | |
3 | |
3 | |
2 |