Issue with Jinja Filter Variable Not Passing Value in Superset Dashboard

[Nethaje]

Bug description

Subject: Issue with Jinja Filter Variable Not Passing Value in Superset Dashboard

Facing an issue while using Jinja templating for a filter variable in a SQL Lab query and visualizing it in a dashboard.

I’ve defined the filter as a Jinja variable using:
{{ experience_threshold | int | default(0) }}
The filter is created manually in the dashboard and linked to the chart.
The experience_threshold is not a column in the dataset—it's a dynamic input only used in the query logic.

Expected Behavior:
The value selected from the dashboard filter should replace the Jinja variable and reflect in the query logic and output.

Actual Behavior:
The query always uses the default value from the Jinja template (0), regardless of the dashboard input.

Could someone help confirm:
If dynamic Jinja filters like this are supported in dashboards?
If so, are there additional configuration steps required to ensure the filter value is passed correctly from the dashboard into the query?

Any guidance or references would be greatly appreciated.

Screenshots/recordings

Superset version

master / latest-dev

Python version

3.10

Node version

Not applicable

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

Hello @Nethaje! 👋 I'm Dosu, your friendly bug-squashing bot here to help tackle issues, answer your questions, and assist with contributions while you wait for a human maintainer. Let's get to work! 🚀

I found a similar unsolved discussion that might be relevant to your issue: Jinja Template, which was last updated on April 22, 2025 ^[1].

Regarding your question, dynamic Jinja filters are supported in Superset dashboards. To ensure the filter value is passed correctly from the dashboard into the query, you can use the {{ filter_values() }} function. This function retrieves the value for a specific filter as a list, which can then be used in your SQL query. For example:

SELECT action, count(*) as times
FROM logs
WHERE
    action in {{ filter_values('action_type')|where_in }}
GROUP BY action

In this example, filter_values('action_type') retrieves the filter values for 'action_type', and the where_in filter converts this list into a string suitable for an IN expression in SQL ^[2].

You might need to adjust your query to use filter_values() to ensure the dynamic input is correctly passed from the dashboard.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}