Skip to content

Allow Default Filter Values to be Determined Dynamically #51295

Open
@ixipixi

Description

Is your feature request related to a problem? Please describe.

We have two different use cases related to this request:

  1. Customer has a question with a date filter and needs to enforce a default date range. They would like for the default month to be "most recent month with data".

  2. Another customer has a dashboard that they are deploying to multiple environments. Each environment contains it's own identical schema, but the contents of the tables (and thus the default values they need to set for each) will vary. The contents of these tables, per customer, may change. They would like to be able to enforce a default text filter that is something like "first not null value in the result set" so that they can deploy all of these dashboard with a functional default filter.

Describe the solution you'd like
Some method of defining the default value dynamically. Perhaps a custom expression, SQL statement or being able to refer to the results of another card for the default.

Describe alternatives you've considered

  • For the deployment case we considered setting the defaults in the YAML files prior to deployment to individual customers. This would add a lot of complexity to the deployment process and the values still wouldn't update with the customers underlying data if it changes.
  • For the date issue, considered relative date filter as a default - but the customer would like the default to change as data for the current month become available.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions