Bug description

Using jinja filters, when i drilldown, the filter is not passed through.

Apache Superset Using jinja filters, when i drilldown, the filter is not passed through.

How to reproduce the bug

  1. Create a jinja filter AND pda.ano in {{ filter_values('ano')|where_in }}

  2. Create a filter Apache Superset Using jinja filters, when i drilldown, the filter is not passed through.

  3. After loading the dashboards, choose drilldown to detail Apache Superset Using jinja filters, when i drilldown, the filter is not passed through.

  4. The error occurs Apache Superset Using jinja filters, when i drilldown, the filter is not passed through.

Screenshots/recordings

No response

Superset version

3.1.1

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
  • [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
  • [x] 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.

Comment From: superlee007

Is there any solution? I have the same problem. My chart has some url_params for jinja filter, but when I drilldown, the filter is not passed through. Tks

Comment From: rusackas

Is this still the situation in 4.1.1? We're no longer supporting 3.x.

Comment From: rusackas

Wondering if this is still happening in new versions, particularly on master since the SQLGlot port has taken place there. This might be closed as inactive/not-planned if we can't get info on the current state of affairs.

Comment From: mbardolia

I seem to be having a similar issue in which the dashboard filter values are not being passed through to a custom where clause I have on my chart when using the Jinja marco filter_values(). I have validated that I am using the correct filter name and that the filter is scoped to the chart. I've added the following debug line which always returns an empty value. -- DEBUG: {{ filter_values("FilterName") }}

I am running version 4.1.1. Any guidance or help would be very much appreciated.

Comment From: mbardolia

Quick update to the above. Instead of using the FilterName, I tried using the column name from the table and that worked.