Forum Discussion

SRJPBI's avatar
SRJPBI
Frequent Visitor
4 months ago
Solved

Power BI REST API - why does my cloud connector call fail with 'BadRequest'?

I have a Power BI report that's been published into the online service. It works fine. I now want to automatically extract data from a matrix within the report.   I have created a flow in Power Aut...
Need Help
  • v-ssriganesh's avatar
    v-ssriganesh
    4 months ago

    Hi SRJPBI,

    Thank you for sharing the details and the updated DAX query.

    Based on the official Microsoft documentation, the Execute Queries REST API requires a valid DAX query that returns a table, typically using a single EVALUATE statement. The query pattern you’re using (DEFINE / VAR with one EVALUATE) is valid DAX syntax.

    When using this API from Power Automate, a 400 BadRequest is commonly caused by request‑formatting issues rather than the DAX logic itself:

    • The DAX query is sent inside a JSON request body, so any double quotes inside the DAX (for example "IsGrandTotalRowTotal") must be escaped (e.g., \"IsGrandTotalRowTotal\") to keep the JSON valid.
    • Only the DAX query should be passed to the API; comments such as // DAX Query should be removed.

    Ensure the request body follows the documented format:

    {
  "queries": [
   { "query": "<DAX query text>" }
  ]
}

    In addition, please verify the documented prerequisites:

    • The Dataset Execute Queries REST API tenant setting is enabled.
    • The calling user has Read + Build permissions on the dataset.

    For troubleshooting, you can also test with a simpler SUMMARIZECOLUMNS query to confirm the API call succeeds before adding more complex logic.

    For your reference: Datasets - Execute Queries - REST API (Power BI Power BI REST APIs) | Microsoft Learn

    Best regards,
    Ganesh Singamshetty

Kagiyama_yutaka's avatar
Kagiyama_yutaka
Icon for Continued Contributor rankContinued Contributor
4 months ago

I think the BadReq comes from the visual DAX dragging calc‑lineage the API can’t read,
so keep only the one EVALUATE table that returns rows—if it still breaks, run that line in DAX Studio n see what op won’t fold.

  • SRJPBI's avatar
    SRJPBI
    Frequent Visitor
    4 months ago

    This doesn't seem to fix the issue. Here is my original code:

     
    // DAX Query
    DEFINE
    VAR __DS0Core = 
    SUMMARIZECOLUMNS(
    ROLLUPADDISSUBTOTAL('Table'[Col1], "IsGrandTotalRowTotal"),
    "SumCol2", CALCULATE(SUM('Table'[Col2])),
    "SumCol3", CALCULATE(SUM('Table'[Col3]))
    )
     
    VAR __DS0PrimaryWindowed = 
    TOPN(502, __DS0Core, [IsGrandTotalRowTotal], 0, 'Table'[Col1], 1)
     
    EVALUATE
    __DS0PrimaryWindowed
     
    ORDER BY
    [IsGrandTotalRowTotal] DESC, 'Table'[Col1]

     

    And here is what I changed it to:

     

    // DAX Query
    EVALUATE
    TOPN(502, SUMMARIZECOLUMNS(
    ROLLUPADDISSUBTOTAL('Table'[Col1], "IsGrandTotalRowTotal"),
    "SumCol2", CALCULATE(SUM('Table'[Col2])),
    "SumCol3", CALCULATE(SUM('Table'[Col3]))
    ), [IsGrandTotalRowTotal], 0, 'Table'[Col1], 1)
     
    ORDER BY
    [IsGrandTotalRowTotal] DESC, 'Table'[Col1]

     

    Both versions return the same error.

     

     

     

     

    • Kagiyama_yutaka's avatar
      Kagiyama_yutaka
      Icon for Continued Contributor rankContinued Contributor
      4 months ago

      thanks for the update — the rewrite isn’t the issue. the query still has visual-only stuff the API can’t read: the subtotal op, the auto-added lineage/total column, and the ORDER BY. executequeries only takes a plain table expression, so those bits have to go.