You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dbsechin (via GitHub)" <gi...@apache.org> on 2024/03/05 13:42:47 UTC
[I] Using jinja filters, when i drilldown, the filter is not passed through. [superset]
dbsechin opened a new issue, #27396:
URL: https://github.com/apache/superset/issues/27396
### Bug description
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
3. After loading the dashboards, choose drilldown to detail
4. The error occurs
### Screenshots/recordings
_No response_
### Superset version
3.1.1
### Python version
3.9
### Node version
16
### 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.
--
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-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Using jinja filters, when i drilldown, the filter is not passed through. [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #27396:
URL: https://github.com/apache/superset/issues/27396#issuecomment-2963729884
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.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Using jinja filters, when i drilldown, the filter is not passed through. [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #27396:
URL: https://github.com/apache/superset/issues/27396#issuecomment-4748664093
This is marked validation:required and overlaps with the broader Jinja-template + drill-down handling tracked in #35263. Closing as lacking-validation. Please confirm on a current releases (6.x) or add details to #35263 if it's the same root cause.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Using jinja filters, when i drilldown, the filter is not passed through. [superset]
Posted by "superlee007 (via GitHub)" <gi...@apache.org>.
superlee007 commented on issue #27396:
URL: https://github.com/apache/superset/issues/27396#issuecomment-2116860831
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
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Using jinja filters, when i drilldown, the filter is not passed through. [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #27396:
URL: https://github.com/apache/superset/issues/27396#issuecomment-2741562739
Is this still the situation in 4.1.1? We're no longer supporting 3.x.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Using jinja filters, when i drilldown, the filter is not passed through. [superset]
Posted by "mbardolia (via GitHub)" <gi...@apache.org>.
mbardolia commented on issue #27396:
URL: https://github.com/apache/superset/issues/27396#issuecomment-3001415730
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.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Using jinja filters, when i drilldown, the filter is not passed through. [superset]
Posted by "mbardolia (via GitHub)" <gi...@apache.org>.
mbardolia commented on issue #27396:
URL: https://github.com/apache/superset/issues/27396#issuecomment-3004920300
Quick update to the above. Instead of using the FilterName, I tried using the column name from the table and that worked.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Using jinja filters, when i drilldown, the filter is not passed through. [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #27396:
URL: https://github.com/apache/superset/issues/27396#issuecomment-4049366343
This hasn't been confirmed as a bug on a currently supported version (5.x or newer). The most recent report (June 2025 on 4.1.1) was resolved by using the column name rather than the filter display name in `filter_values()` — it might be worth double-checking that the correct argument is being used.
If you can still reproduce this on Superset 5.x with the correct `filter_values()` argument (column name, not display name), it would be great if you could share a minimal reproduction here. Without that, this issue may be closed as inactive. Last activity was approximately 8.5 months ago.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Using jinja filters, when i drilldown, the filter is not passed through. [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #27396: Using jinja filters, when i drilldown, the filter is not passed through.
URL: https://github.com/apache/superset/issues/27396
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org