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 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.
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.
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.
Hi Nicke, any further updates here? This has put a serious wrench in our product plans too.
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!
