Getting visual has exceeded the available resource error on Power BI Service for a visual

[Anonymous]

Hi All,

I have created a model with few dimensions and one fact table. The fact table is huge so cannot load it using import mode so kept it in direct. Rest all dimensions are set to import (also tried dual). When creating a visual by pulling the data from 2 dimensions and amount field from fact, it is throwing an error (visual has exceeded the available resource). When checked the details, it is getting timeout after 225 secs. I tried adding command timeout to an hour in power query for all the tables but still getting same error on Service. On desktop, it worked when i changed the query limit simulation to no limit but on service, it is not working. I am using premium P1 capacity. Is there any way to increare the query timeout from 3mins to max so that it will not throw any error and load the data ?

Any help would be really appreciated!!!

[lbendlin · Accepted solution]

Examine the Direct Query queries in DAX Studio and optimize your datasource accordingly.

Note that when dimension table join keys have cardinality over 50K performance will degrade.

[Anonymous · Accepted solution]

Hi @Anonymous ,

"This visual has exceeded the available resources" error message indicates that the query or the computation it involves consumes more memory than the limit configured in Power BI.

There are two possible solutions:

1.Refer to the official documentation provided:

Troubleshooting tile errors - Power BI | Microsoft Learn

2.Optimize the model and the query as @lbendlin said.

For more detailed information on optimizing Power BI models, see the following documentation:

Optimization guide for Power BI - Power BI | Microsoft Learn

Improve Power BI Performance by Optimizing your DAX | by MAQ Software | MAQ Software | Medium

How to Optimize Dax Queries in Power BI - Zebra BI

If you have any other questions please feel free to contact me.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[lbendlin · Accepted solution]

Examine the Direct Query queries in DAX Studio and optimize your datasource accordingly.

Note that when dimension table join keys have cardinality over 50K performance will degrade.