Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
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
User | Count |
---|---|
5 | |
4 | |
3 | |
2 | |
2 |
User | Count |
---|---|
8 | |
6 | |
4 | |
4 | |
4 |