Forum Discussion
Table Visual unable to load data despite having fewer rows.
Hi SaiK ,
Probably, the second table contains some DAX calculations that are consuming a lot of resources. I recommend carefully reviewing the calculations in that table to identify any potential performance issues.
Additionally, you can use the Performance Analyzer to assess the table's performance and determine which queries or measures are impacting efficiency.
Thanks for the prompt response. But this is very weird considering both the tables are using different parameters and the rest all features are same, despite having less data the table is not rendering. Shall try this out and update you about the same.
- Bibiano_Geraldo1 year agoSuper User
I understand, that does seem strange, especially if the tables are using different parameters and the rest of the settings are similar. The fact that one table isn't rendering, even with less data, could be due to another factor like the complexity of the calculations or filters applied.
Try using the Performance Analyzer to identify where the issue might be, and if the calculations are correct, it might also be worth checking for any issues with the table indexes or relationships. Let me know how it goes!
- SaiK1 year agoHelper I
Hi,
The DAX query is taking 225934ms for this table. But the query for both the tables is the same. Another thing is as soon as I remove the pagination filter from the table, it is rendering fine. The pagination filter(which restricts the amount of items displayed on the page). Also the table is rendering the data if I limit the amount of rows to top 5000.- Bibiano_Geraldo1 year agoSuper User
Hi,
It looks like the pagination filter is impacting performance. Since removing it allows the table to render and limiting rows to 5000 works, the issue might be how the filter interacts with the dataset. Even if the DAX query is the same, Power BI could be handling rendering differently due to filters. Try checking how the pagination filter is applied, whether it adds extra processing, and if the query can be optimized. Running the Performance Analyzer while toggling the filter might give more insights. Let me know what you find!