DAX Info Functions Against Published Datasets

[rjhale]

Hello,

As part of a Power Automate Flow that we setup months ago, we were using the new DAX Info functions to pull metadata regarding partitions and expressions.  These queries have been working without issue until this past weekend.  Here is an example of a simple DAX query that would return information about the queries loaded to the data model:

For the last couple of days, these have failed to execute with a generic error stating "Failed to execute the DAX query" and an Analysis Services Error Code of 3239575574.  We have a lot of other Flows that run DAX queries against a dataset in this manner, and those have had no issues.  

Any ideas what may be preventing these queries from executing properly? 

[Nicke]

I have the same issue too. Does anyone has any clue why and what to do? Is it a bug or a deprecation?

[hmayer156789]

Same Problem here - we had a DAX query with InfoFunctions to get the last refresh of a Table running for Month running via REST API on Pruduction and today it started failing

[pzw512]

I can confirm I got the exact same issue. We use this INFO.PARTITIONS for reporting and impact analysis when we change and/or modify data sources. Was quite practical, but since the beginning of this week it returns a 400 bad request. . Other  DAX queries accessing dataset tables work fine though. 

[nigeldavidmaxey]

I've hit the very same problem. We had just put a production Python data ingestion in place to extract the queryDefinition from all datasets and ingest into Snowflake. From that we could extract Snowflake database/schema/model, native queries, Sharepoint etc. That meant we could get a full overview in data sources used in our publish PBI datasets.

Now without warning that functionality does not work.

I can do some of it on a local script (on Windows with ADOMD) or per dataset with DAX Studio. However it does leave our recent production implementation redundant until we have a viable alternative. Surely it shouldn't be so difficult to get this partition data!

[plusselmann]

Same problem here.

We are a startup building iOS application to be able to integrate data from Power BI using REST API.

We built this application and deployed to users.

Till last week this was working fine.

This is unacceptable to hear from my last Support call, that Product team does not know if it will be fix and by when.

We have users completly blocked because this API calls now retrun 400 Bad Request.

We need a work around, we are OK to use any other API if needed but we need to be able to get metadata from a Semantic Model with executing INFO.VIEW.COLUMNS( ) and INFO.VIEW.MEASURES( ).

Especialy this is working fine in DAX Studio.

I hope to get a better answer rapidly.

[Nicke]

If anybody is interested I got another answer today. 

Greetings for the day! I hope you’re having a wonderful day. We understand the difficulty you're facing with the situation where the feature was previously working and has suddenly stopped. It must be incredibly challenging for you, and we sincerely apologize for the inconvenience.

The product team mentioned that they cannot revert the changes since it will introduce a security problem. We are currently checking if there is any ETA for a fix. As soon as we get any information from them, we will promptly update you.

We genuinely appreciate your cooperation and support during this time. Thank you once again for your patience and understanding.

[drewgillson]

Hi Nicke, any further updates here? This has put a serious wrench in our product plans too.

[Nicke]

Nope, I've sent a new request today for the ETA but haven't got any answer yet. Also asked for a link to known issues that they should provide.

[nilendraFabric]

Hello @rjhale 

It looks like the issue with DAX Info functions failing to execute against published datasets is caused by a bug introduced in the November 2024 update (version 2.138.782.0) of Power BI Desktop. This bug specifically affects the execution of DAX Info functions like CALENDARAUTO when opening certain files.

https://www.reddit.com/r/PowerBI/comments/1gqtl7m/nov_update_20241111_throws_unable_to_execute_dax/

To resolve this issue:
1. Revert to the October 2024 build (2.137.1102.0) of Power BI Desktop, which opens affected files without complications.
2. Wait for the January 2025 update of Power BI Desktop (Version: 2.139.1678.0), which has fixed this issue.
3. If using the latest version, modify your DAX code to avoid using CALENDARAUTO and instead use alternative methods for creating date tables.

hopefully this resolves your query. 

Please accept this solution and give kudos, if you find this helpful 

[rjhale]

I don't think this is the same issue as outlined in that Reddit thread.  The issue I described went from successfullly executing on 50+ datasets to failing on those same datasets sometime between last Friday and Monday morning.  These would have been datasets published with older version of Power BI desktop and possibly a few since the November release. 

Just to be sure though, I did update to the January release, republished one of the datasets, and retried the DAX query: EVALUATE SELECTCOLUMNS(INFO.PARTITIONS(), [QueryDefinition]).  It still fails with the same error message.  

My suspicion is that something changed with the analysis service engine or maybe a new security policy.