Forum Discussion

Matthias93's avatar
Matthias93
Icon for Helper III rankHelper III
9 years ago

Report is too slow

Hi, I currently have a dashboard based on 5 excels and 10 SharePoint lists. To increase the speed of this report I have done mulitple things:    Deleted columns I don't need (will it make a diffe...
Need Help
Anonymous's avatar
Anonymous
Not applicable
9 years ago

Hi Matthias93,

 

It seems like I provide a low performance method, you can try to use below method if it has better performance.

 

1. Add calculate column and measure to get the current value.

 

Measure: calculagte the total hours.

Total =
var temp= LASTNONBLANK(Table1[Team Member],[Team Member])
Return
SUMX(FILTER(ALL(Table1),Table1[Team Member]=temp),[Number of hours])

 

Calculate column:

Current Value =
[Number of hours]*[Question 1 Value]/[Total]

 

 

 

2. Summary the table.

Summary table= SUMMARIZE(Table1,[Team Member],"Result",SUM(Table1[Current Value]))

 

 

 

Regards,

Xiaoxin Sheng

Matthias93's avatar
Matthias93
Icon for Helper III rankHelper III
9 years ago

Hi,

 

I tried this and it seems to be working nicely. I have the impression performance has improved, but it can still be quite slow. This could indeed be due to the slicers I have on each page.

 

Thanks for helping me out!

 

Kind regards,

Matt

  • Ermin's avatar
    Ermin
    Icon for Advocate II rankAdvocate II
    9 years ago

    Hi @ Matthias93,

    As said I have an impression that the number of slicers and dependency between the slicers and the charts play a significant role in the report performance. I have performance issues on one of my report although I don’t have any measures or significant calculations and the number of data is way lower than what I usually have. The only difference to my other reports  is number of slicers.  

     

    Try duplicating your report to another tab then remove few slicers and test performance again. I’m sure that the performance will improve. This will just help you answer the question, Is it the number of slicers or the calculation intensive measure causing the performance issues.  

     

    If it is number of slicers, then we both have another issue which I have no clue how to resolve J. Maybe a new post or bug report to Microsoft will help.  

     

    Regards,

    Ermin

  • Matthias93's avatar
    Matthias93
    Icon for Helper III rankHelper III
    9 years ago

    Removing all slicers but one did indeed make the report faster, but still not fast enough in my opinion, especially when considering how small my dataset is at the moment. The slicers always cross-filter when you make a selection, this indeed eats up a lot of the performance. 

     

    Kind regards,

    Matt