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