Forum Discussion
DAX Info Functions Against Published Datasets
I've had an open support request with MS since this started happening back in January. I recently started up the conversation again, and I just heard from their engineers this morning that they fixed the issue. I checked our Power Automate Flow has been failing on that step since January, and it did successfully run this morning. It seems that the issue should be resolved now.
Hello,
INFO Dax functions are blocked in Execute Query API. Microsoft confirmed the same in my support ticket. MS product team mentioned that it was blocked because of security concern
Thanks
I got this from support:
Thank you for your response, and I apologize for any confusion.
We have received an update from the team indicating that the INFO functions depend on Dynamic Management Views (DMVs), which are not supported by the Execute Queries REST API. However, we understand that customers were able to use these functions before the recent update to the Execute Queries REST API.
The changes are considered to be by design, and we won't support the use of INFO.* within Execute Queries going forward. However, our product team is diligently working on a fix to support the INFO family of functions with the Execute Queries REST API in the near future, although we don't have an exact timeline yet.
Please try using the workaround suggested by our product team and let us know the outcome. Once again, we sincerely apologize for any inconvenience this may have caused.
Thank you once again for your understanding. If you have any further questions or need assistance, please don't hesitate to reach out.
😡, ok Microsoft, you stop the work the function and it's ok?
Thanks Nicke.
What was the workaround suggested by the product team?
Here is the previous answer, not a viable option for us unfortunately.
We got an update from our product team that a recent update to the Execute Queries REST API has caused DAX queries using the INFO family of functions to return HTTP 400 or similar errors. We recognize how disruptive this can be to your workflow and sincerely apologize for inconvenience this may have caused.
The INFO functions depend on DMVs, which the Execute Queries REST API has not supported. However, we acknowledge that customers were able to use these functions prior to the recent update.
It's clear from Datasets - Execute Queries - REST API (Power BI Power BI REST APIs) | Microsoft Learn that "Only DAX queries are supported at this time. MDX and DMV queries are not supported." so this is a restriction that was not previously implemented.
As a workaround, if your model is in premium, you might be able to switch your solutions to XMLA Endpoint-based connections and query semantic models using the AS client libraries (ADOMD.NET).
We appreciate your patience and understanding as we work through this issue. If you need further assistance or have any questions, please do not hesitate to reach out. We are here to help.
That's interesting. So if I'm understanding this correctly, they plan to simply drop support for something they advertised as a new feature in the Power BI service only 6 or 7 months ago? This is incredibly frustrating if that's the case.
Did they provide any guidance on how to query semantic models using the AS client libraries? It would be helpful if there was some way to do this through Power Automate as our previous solution was executing those Info queries from a scheduled Flow.
Monumentally frustrating this. We have a PowerApp that use these functions to get the list of tables and partitions so we can selectively refresh them instead of the whole model.
Another answer,
We truly understand the challenges you are facing, and we sincerely apologize for any inconvenience this situation has caused.
Yes, as our team mentioned, they are working on a fix to support the INFO family of functions with the Execute Queries REST API in future. While our team is dedicated to resolving this issue as swiftly, we unfortunately do not have a precise timeline for when this fix will be implemented.
We appreciate your patience and understanding.
