Smart(er) filter default

Currently, there is some logic to default to the type of filter (date range if it is a date, list/exclusion for string, range for numeric, etc.). However, many primary/foreign keys which should likely be filtered by a list/exclusion are defaulted to a numeric range.

It is a very low-priority request, but hundreds of filter changes can cause reporting fatigue – and it seems like a fairly straight-forward improvement.

Hi Kellen, would changing the data type of those columns help resolve the default? For example, changing the keys to strings which would default to a list/exclusions.