Forum Discussion

Semail's avatar
Semail
Regular Visitor
4 months ago
Solved

Power BI Service: DirectQuery (Kusto) visuals fail online but work fine in Desktop

Hi everyone,   I’m facing an issue with a Power BI FinOps dashboard using DirectQuery to Azure Data Explorer (Kusto). The report works perfectly in Power BI Desktop Dataset refresh in the Servic...
Need Help
  • v-achippa's avatar
    v-achippa
    4 months ago

    Hi Semail,

     

    Thank you for the detailed response. Here the issue is related to the DirectQuery in the service because of the strict resource and concurrency limits compared to desktop. Since each visual sends its own query, multiple complex visuals running in parallel can exceed those limits and error occurs.

    Since kusto changes are limited in your case, please try the below steps on the power bi side:

    • Reduce the number of visuals per page to limit parallel queries
    • Simplify DAX measures to avoid complex query translation
    • Avoid high cardinality slicers and heavy cross filtering
    • If possible, consider a hybrid model like Import with DirectQuery to reduce the load

     

    Thanks and regards,

    Anjan Kumar Chippa

Semail's avatar
Semail
Regular Visitor
4 months ago

Hi everyone v-achippa cengizhanarslan mh2587 ,


thanks a lot for the feedback so far - really appreciated!

I’ve verified that there are no query or visual limits configured.

 


- Regarding query result caching, as far as I understand it, it only works for Import semantic models on Premium/Embedded, while our model is DirectQuery, so I think this doesn’t apply in our case.

- The pre‑aggregation / materialized views in Kusto approach makes sense, but our Kusto setup is based on a standard FinOps template and is not directly managed by me, so changes there may be limited. At this point, the big question is also which part should be adjusted and how, without breaking the standard setup. 

That’s why I was hoping for alternative options that don’t require changes in Kusto.

If Kusto changes are not feasible, are there any Power BI–side optimizations you would recommend for DirectQuery scenarios?

Thanks again! 🙂

v-achippa's avatar
v-achippa
Community Support
4 months ago

Hi Semail,

 

Thank you for the detailed response. Here the issue is related to the DirectQuery in the service because of the strict resource and concurrency limits compared to desktop. Since each visual sends its own query, multiple complex visuals running in parallel can exceed those limits and error occurs.

Since kusto changes are limited in your case, please try the below steps on the power bi side:

  • Reduce the number of visuals per page to limit parallel queries
  • Simplify DAX measures to avoid complex query translation
  • Avoid high cardinality slicers and heavy cross filtering
  • If possible, consider a hybrid model like Import with DirectQuery to reduce the load

 

Thanks and regards,

Anjan Kumar Chippa

  • v-achippa's avatar
    v-achippa
    Community Support
    3 months ago

    Hi Semail,

     

    As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have  provided for the issue worked? or let us know if you need any further assistance.

     

    Thanks and regards,

    Anjan Kumar Chippa