Coherence in filter values on lots of data

[paoliniluis]

Describe the bug

There's an interesting case on filters: let's say that you have a lot of unique values in the data that exceed the limit we have. If that happens we'll show a search box or an input box as the default behavior of the filter.

But you can currently override that: do a question (SQL or GUI), then add the filter and tell the filter to use the values of the query (yes, you'll lose cascading filters in this way), but you made your filter now to use tons of values

To Reproduce

see above

Expected behavior

We should make this behavior coherent, or just put the documentation together to make this a supported use case for big filters

Logs

NA

Information about your Metabase installation

since... forever

Severity

P3

Additional context

No response

[mazameli]

What would "make this behavior coherent" look like in your mind, @paoliniluis? Tell the user "woah, this is gonna be a ton of options in this filter"?

[paoliniluis]

@mazameli I know that this one is tricky, but one of our customers has been hammering on this one for a while. I believe we should chat with them to see what’s their suggestion since:

1. there are a lot of unique filter values and that’s why we show a search box
2. they seem to need all those filter values and that will clog their browser, but that’s why they get all those values via a query