I have a Data Explorer report using 2 date parameters with hard-coded default values. -- [params] -- date :start_date = 2024-12-01 -- date :end_date = 2025-01-01 The hard-coded default values work for most of the parameter types, but for the date parameters, I wish we could set dynamic values,…

I would say you are going to need to “fork” the report, have a specific one that offsets correctly based on current date for data explorer and then a second report for manual usage. I know it is a bit annoying having copies, but it feels like the simplest solution.

Thanks Sam, this is exactly what I was hoping I could avoid. But it is a solution nevertheless : ) I expect I’ll be creating lots of reports in following months. We’ll see how annoying it will get maintaining those “forks”. :wink:

Would it work to move the defaults into the query and use them as long as no date is selected? So, something like this: -- [params] -- null date :start_date -- null date :end_date SELECT id as topic_id, created_at FROM topics WHERE created_at > COALESCE(:start_date, CAST(date_trunc('week', current…

Dynamic params to use with Data Explorer

Community Building Data & reporting

sam (Sam Saffron) February 6, 2025, 8:50pm 4

If the number becomes high, one great approach is to use discourse api to configure it and keep the source in github. That way you also get to carry history and avoid the manual forking.

Topic		Replies	Views
How to add query parameters to Data Explorer? Development	7	1193	November 25, 2020
Syntax for Data Explorer params in Automation Bug	6	301	March 14, 2025
Populate Data Explorer params with URL params Feature data-explorer , completed	12	1788	September 3, 2025
Data explorer group report - parameter bug Bug data-explorer	7	884	December 28, 2022
"DataExplorer::ValidationError: Missing parameter end_date of type string Product Support	2	924	May 27, 2020

Dynamic params to use with Data Explorer

Related topics