Description

Table explores can have required filters, but much like dashboards, sometimes I want to suggest filters to my end users, that they can remove if they want to. As such, allowing a recommended filter to be set, that can be removed by the user.

What problem does this solve?

This should make self serve more intuitive for business users.

If building this feature, it seems that we should:

Allow another option at the model meta level - the default_filter. See screenshot below for how this might look:

Note that the default filter would include required filters - and make the old required_filters option legacy. Users would just add some config within a default filter to make it required.