I have a list of millions of rows/transactions and each transaction relates to a postcode. There are up to 500,000 distinct postcodes use in any year.
I have created visualisations and tables with this data set and filtered out all postcodes bar the one(s) I might be interested in. It worked and because of the large number of postcodes, it seems to work better than using a slicer. I have created helper columns for the initial letter of a postcode and another one for the first two characters of a postcode and they help with slicing but filtering is more direct in that case.
My question relates to the New Quick Measure and creating a filtered value. In order to filter using my postcode of interest, I would need to scroll down the list but that is tedious and I can see it would take a long time if, for example, my postcode of interest starts with the letter H or I or J, in the middle of the alphabet.
So, is there a quick and direct way of filtering the database in a New Quick Measure as there is in what I might call an ordinary filtering situation?
