ShivamYadav0 opened a new issue, #35263:
URL: https://github.com/apache/superset/issues/35263
### Bug description
I'm working with three separate datasets, each built using Jinja templating
to support dynamic filtering. These datasets are used to power three different
charts in a dashboard. All charts share common filter fields (e.g., start_date,
Zone, Circle, etc.), and I’ve configured native filters to apply across all
charts.
Each dataset uses Jinja to apply filters like this:
**SQL query** is something like this in all 4 datasets.
_WHERE 1=1
{% if filter_values('Zone') %}
AND "Zone" IN {{ filter_values('Zone') | where_in }}
{% endif %}_
The charts display correct data when filters are applied. However, when I
use Drill to Detail or Drill by on any chart, the resulting detail view shows
zero records, even though the chart clearly shows data for the selected value.
**Expected Behavior**
Drill to Detail should return the filtered rows from the dataset that match
the clicked chart element (e.g., Circle = C1, type_of_node = A).
**Actual Behavior**
Drill to Detail and Drill by return no rows, even though the chart shows
non-zero values. This happens consistently across all three charts.
**Notes**
1. All datasets use Jinja templating for dynamic filters.
2. All charts are built from separate datasets, but they share common column
names and filter logic.
3. Native filters are scoped correctly to all charts.
4. The issue seems to be with how Superset applies drill filters to
Jinja-based queries across multiple datasets.
### Screenshots/recordings
_No response_
### Superset version
4.1.3
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
<img width="1622" height="843" alt="Image"
src="https://github.com/user-attachments/assets/c03405bb-d9cb-43db-ab8f-96172019b960";
/>
### Checklist
- [ ] 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.
- [ ] 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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
