Forum Discussion
Using measure as filter causes visualisation to hang
You can see that the date filter is picked up and although referenced in SUMMARIZECOLUMNS isn't reducing the row set at all. Everything gets computed for every row and then at the end that table only keeps rows with [Measure] = 1.Thanks bcdobbs but why doesn't that logic hold for the unfiltered table where the rows are sorted by the measure? It generates quickly in that situation, but doesn't it have to calculate every row just as you mention above for the filter?
Thanks
You're right certainly not answered yet!
Can you share the full query that the performance analyser when the matrix hangs?
Does it hang when you just have the filter measure or do you only get the issue when you have everything in?
- Anonymous4 years agoNot applicable
Can you share the full query that the performance analyser when the matrix hangs?
The "Copy query" button in performance analyzer is ghosted out, a bit frustrating as it must know the query that it is trying to run??
Does it hang when you just have the filter measure or do you only get the issue when you have everything in?
It only hangs when I have everything in. If I just have the filter measure (and a fact table field) then it's runs quickly.
- bcdobbs4 years ago
Community Champion
Something odd there! Can you share the code for each measure. Running out of ideas but that might at least spark a line of enquiry!
- V-lianl-msft4 years ago
Community Support
Hi Anonymous ,
You can try importing performance analyzer data in dax studio, simplifying the analysis of slower queries in a report.
https://www.sqlbi.com/articles/importing-performance-analyzer-data-in-dax-studio/
Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.