saurabh1-singh opened a new issue #8892: Jinja Template not working in case of 
view query
URL: https://github.com/apache/incubator-superset/issues/8892
 
 
   When I put the jinja template inside a filter after selecting a table data 
source directly and then use a filter box to fill those values at runtime it 
works fine. But when I create a advanced query i.e. view, then the same thing 
does not work.
   ![Screenshot from 2019-12-24 
13-51-04](https://user-images.githubusercontent.com/42036742/71403279-3fa3da80-2655-11ea-9cc3-9205f839951f.png)
   
   In the above screenshot you can see the char test_char is loaded fine but 
not the test_c_1
   
   ![Screenshot from 2019-12-24 
13-54-04](https://user-images.githubusercontent.com/42036742/71403282-403c7100-2655-11ea-88f0-90f6ab356910.png)
   
   The above one is test_c_1 with a advanced query/view
   
   ![Screenshot from 2019-12-24 
13-55-08](https://user-images.githubusercontent.com/42036742/71403283-403c7100-2655-11ea-81b3-88f4af2bc0fc.png)
   
   
   ### Expected results
   
   I expected both to work similarly
   
   ### Actual results
   
   Did not happen in case of view it also creates an extra filter with the name 
of the filter in filter box and try it apply it too
   
   #### Screenshots
   
   If applicable, add screenshots to help explain your problem.
   
   #### How to reproduce the bug
   
   1. Go to '...'
   2. Click on '....'
   3. Scroll down to '....'
   4. See error
   
   ### Environment
   
   (please complete the following information):
   
   - superset version: `superset version`
   - python version: `python --version`
   - node.js version: `node -v`
   - npm version: `npm -v`
   
   ### Checklist
   
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [ ] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [ ] I have reproduced the issue with at least the latest released version 
of superset.
   - [ ] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   Add any other context about the problem here.
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to