Summary
Metabase currently supports a single date picker for SQL parameters, but it does not natively support a date range picker. Adding a date range parameter would significantly improve usability for dashboards and SQL questions that require filtering between two dates.
Problem
Many analytical queries require filtering data between a start date and end date. In the current implementation, users must create two separate parameters (e.g., start_date and end_date). This approach has several drawbacks:
-
It increases complexity in SQL queries.
-
It creates a less intuitive user experience on dashboards.
-
It requires additional filters and manual coordination between parameters.
-
It becomes harder to reuse questions across dashboards.
For example, instead of writing a simple filter, users must do something like:
WHERE Date BETWEEN {{start_date}} AND {{end_date}}
This forces dashboard users to manage two filters instead of one unified range selector.
Proposed Feature
Introduce a Date Range SQL Parameter Type that allows users to select both the start and end date within a single filter control.
Example usage:
WHERE Date BETWEEN {{date_range.start}} AND {{date_range.end}}
Or alternatively:
WHERE Date BETWEEN {{date_range}}
where {{date_range}} automatically expands to the appropriate start and end values.
Benefits
-
Better User Experience
A single date range picker is more intuitive and standard in analytics tools. -
Cleaner SQL Queries
Queries become easier to read and maintain. -
Simpler Dashboard Filters
Dashboards can use a single control rather than two separate parameters. -
Parity with Other BI Tools
Many BI tools (Power BI, Looker Studio, Tableau) support a native date range filter. -
Improved Reusability
Questions can be reused across dashboards without managing multiple date parameters.
Example Use Cases
-
Sales between two dates
-
Campaign performance during a specific period
-
Monthly or quarterly reporting
-
Trend analysis
Conclusion
Adding a Date Range SQL Parameter would greatly improve query simplicity, dashboard usability, and overall analytical workflows in Metabase. It would also align Metabase with standard filtering capabilities available in other modern BI platforms.
This feature would be particularly valuable for teams that rely heavily on SQL questions and dynamic dashboards.