Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.

Bug Report - Unable to use INFO() DAX functions with ExecuteQueries REST API

Per the following thread: Re: DAX Info Functions Against Published Datasets - Microsoft Fabric Community

 

It seems that we're unable to execute any of the INFO() DAX functions when using the ExecuteQueries REST API on a published semantic model. I have a few pipelines that require extracting metadata from the semantic model, and everything was working fine until this morning when I started getting an Analysis Services error code of "3239575574" (below is the full JSON of the error message).

 

 

{
"error": {
"code": "DatasetExecuteQueriesError",
"pbi.error": {
"code": "DatasetExecuteQueriesError",
"parameters": {},
"details": [
{
"code": "DetailsMessage",
"detail": {
"type": 1,
"value": "Failed to execute the DAX query."
}
},
{
"code": "AnalysisServicesErrorCode",
"detail": {
"type": 1,
"value": "3239575574"
}
}
]
}
}
}

Status: Accepted

Hi @TheDataBrick ,

Based on the latest update from our internal team, the fix is currently scheduled for March 24, 2025. In the meantime, I will keep you updated on any further developments or changes. Please don’t hesitate to reach out if you have any questions or need additional assistance.

Best Regards

Comments
v-yiruan-msft
Community Support
Status changed to: Investigating

Hi @TMJForrester ,

The issue has been reported to the internal team, they are working on a fix. We understand the inconvenience this may have caused and sincerely apologize for any disruption. Rest assured, we will provide further updates as soon as they become available. Thank you for your patience and understanding.

Best Regards

 

nfredette101
Regular Visitor

Following along as we noticed this with DMV queries where we gather the partition names.  We'll switch to the info tables but those are not working either.

v-yiruan-msft
Community Support
Status changed to: Investigating

Hi @TMJForrester & @nfredette101 ,

The related team is working on temporary solution for selected tenants/capacities, I will update you once the relevant testing and validation is done.

Best Regards

TheDataBrick
New Member
Bumping this thread to receive updates on the status of this issue. Are there any other known ways of achieving this information in an automatic fashion?
v-yiruan-msft
Community Support
Status changed to: Accepted

Hi @TheDataBrick ,

Based on the latest update from our internal team, the fix is currently scheduled for March 24, 2025. In the meantime, I will keep you updated on any further developments or changes. Please don’t hesitate to reach out if you have any questions or need additional assistance.

Best Regards