Re: [I] Jinja execution is not happening when a dataset "sync columns" feature is used [superset]

["biffhero (via GitHub)" <gi...@apache.org>]

biffhero commented on issue #25839:
URL: https://github.com/apache/superset/issues/25839#issuecomment-2591521614

   I was able to perform a workaround.  Create the query in SQL Lab, add the default parameters to the SQL Lab, verify it works.  Save it, go to the dataset browser.
   
   In the dataset browser, edit the dataset, unlock the query.  Go to the query, cut out the Jinja parameters, sync the columns.
   
   Replace the Jinja parameters, save the dataset.  Go to the charts, the columns are available to use.
   
   I agree with developers if they were to say "There's a workaround, this isn't a huge problem."  I'd like to see the sync button submit the query without the Jinja parameters, read the column types, and then put the Jinja parameters back.  Would that be possible?


-- 
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