Forum Discussion

DMSJennifer's avatar
DMSJennifer
Icon for Helper I rankHelper I
4 years ago
Solved

Error: Resource Governing

Hello,   I'm trying to load some data into my visual, but when I want to view a lot of data, my visual shows the following error:   More information: Resource Governing: This query uses more mem...
data protection
Need Help
  • V-lianl-msft's avatar
    V-lianl-msft
    4 years ago

    Hi DMSJennifer ,

     

    Depending on the data source and the number of fields (measures or columns), a visual may load slowly. We recommend limiting visuals to 10-20 total fields, both for readability and performance reasons.

     

    The upper limit for visuals is 100 fields (measures or columns). If your visual fails to load, reduce the number of fields.

    https://docs.microsoft.com/en-us/power-bi/visuals/power-bi-data-points 

     

    Best Regards,
    Liang
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

cpwebb's avatar
cpwebb
Icon for Microsoft Employee rankMicrosoft Employee
2 years ago

The amount of time it takes the query to run is irrelevant. The problem is that there is something - probably to do with the way you have written the DAX for your measures - that is causing a huge memory spike when the query for the matrix is run. It can be something like adding a zero to all your measures:
https://blog.crossjoin.co.uk/2024/07/07/dax-measures-that-never-return-blank/
or using FILTER with CALCULATE:
https://blog.crossjoin.co.uk/2024/06/30/calculate-filter-and-dax-memory-usage/
or having a table or matrix with a scrollbar:
https://blog.crossjoin.co.uk/2024/07/14/why-power-bi-table-visuals-with-scrollbars-can-cause-problems/


Can you post the DAX for your measures?

jasiluka12's avatar
jasiluka12
Icon for Helper I rankHelper I
2 years ago

yes i managed to discover the issue that allows to load the visual... at least for now ...

 

The problem was that in some of my measures i had a variable as :

VAR _AddNulls =  IF ( ISINSCOPE ( Dim_Accounts[KEY ACCOUNT] ) = FALSE, 0, BLANK () )

 and then at the bottom i had a SWITCH statement based on KEY ACCOUNT with some of them having + _AddNulls at the end. 

removing this _AddNulls variable helped to load the visual again.. although its not ideal as business requirement was to display 0 instead of blanks. 

 

I get that the syntax is not perfect and numerous switch + isinscope statements lead to performance degradation.. however I cant think of a better way to display Profit and Loss table for example.

 

Precalculating it in a table or external paid visuals are not the suitable options in my case so i had to rely on Matrix visual + DAX.