rluech commented on issue #33203:
URL: https://github.com/apache/superset/issues/33203#issuecomment-2826895874
Issue is solved. Jinja template is processed in custom column as expected.
@rusackas it is actually a physical dataset with custom columns (not a
virtual dataset) .
@Vitor-Avila the error occurs already on chart level. Good question, that
helped.
The chart query shows that the jinja template was evaluated es expected and
there is a plain string in place of the jinja template.
The solution is simple, in the sql expression of the custom column, I
replaced:
`"User Principal Name" = '{{ current_username() }}'`
with:
`CASE WHEN "User Principal Name" = '{{ current_username() }}' THEN 1 ELSE 0
END`
--
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]
