Forum Discussion

Uniqueusername's avatar
Uniqueusername
Icon for Helper III rankHelper III
2 years ago
Solved

Error - visual as exceeded the available resource

Hi,   I am having a problem where I get this error message saying that "visual as exceeded the available resources. Try filtering the amount of data displayed". I haven't had this happen previously...
Need Help
  • Uniqueusername's avatar
    Uniqueusername
    2 years ago

    I managed to fix it I think. I changed the storage mode for my aggregated tables from direct to import. The dimensions are in import mode as well. Once I made the changes the interactions between the various visual elements are really quick

     

    However, the granularity of the table rolled up to a high level. Going down further might cause the same issues again. I will test this further but for now it appears to be working

     

     

Uniqueusername's avatar
Uniqueusername
Icon for Helper III rankHelper III
2 years ago

Looks like I have to revisit this post of mine as I have started encounter performance issues

 

 

Firstly, here is a brief explanation of my model when the performance was great - filters were getting applied instantly, cross filtering had no issues. I tried to model my tables as per some of the guidelines and resources I found online ( https://dax.tips/2021/09/06/intro-to-power-bi-aggregations/ )

 

1) AGG_FACT  in import mode

2) Date table in import mode

3)Main_Fact Table in Direct query mode

5) Dimensions in dual mode

 

Using this setup I had no issues. I played around with DAX studio using the limited knowledge of the tool I have and found that the aggregations tables were being referenced where necessary

 

Now, in this model, the AGG_FACT table is an SQL source imported by directly writing a query in the data import stage,.i.e, in the Transform Data stage,  I connect to the server, specify the database name and write an SQL query to generate the aggregated tables which eventually gets imported into Power BI

 

Everything was working smoothly until I tried to tweak my approach a bit. The only change I made was writing a query to create a view directly in  SQL (SSMS) and then importing that AGG_FACT view into power bi. The query I use to create the view is the same query I wrote previously in the import stage

Is there any reason for the performance to get affected ? I mean it is still essentially the same AGG_Fact table with the only difference being the data being imported is the AGG_Fact view from SQL

 

Any help would be much appreciated