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.
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.
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.