Forum Discussion
Using measure as filter causes visualisation to hang
Hello, I have a measure in a visualisation filter, so that I can select only records that are in a date range (selected in a slicer) (i.e. count = 1). The measure uses USERELATIONSHIP to link the...
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