rluech opened a new issue, #33203:
URL: https://github.com/apache/superset/issues/33203
### Bug description
I can successfully use jinja template in SQL Lab and Row Level Security. For
example, this works fine:
`select * from schema.table where "User Principal Name" = '{{
current_username() }}'`
I can also set a custom column to a dataset with "SQL EXPRESSION":
"User Principal Name" = '{{ current_username() }}'`
However, when I use this custom column as a dashboard filter I get the DB
Error: "FROM keyword not found where expected". Based on the related Q&A and
issues I wonder if there is a bug in the jinja template processing on datasets?
related:
[Q&A 32215](https://github.com/apache/superset/discussions/32215)
[Q&A 30448](https://github.com/apache/superset/discussions/30448)
[issue 25786](https://github.com/apache/superset/issues/25786)
[fix 33195](https://github.com/apache/superset/pull/33195)
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### 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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
