Unable to run query after passing url_param parameters to sql_lab query. Button does not do anything.

This functionality used to run in 0.28 version, however after upgrading to 0.35 it not running anymore.
Are these fields supposed to be pre-filled using url_param?

Can some one please help with this, if possible please post some examples on how to pass url_param in newer version.
A clear and concise description of what the bug is.
what you expected to happen.
what actually happens.
If applicable, add screenshots to help explain your problem.
(please complete the following information):
0.35.13.6node -vnpm -vMake sure these boxes are checked before submitting your issue - thank you!
Add any other context about the problem here.
Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.84. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
There was a fix related to url_params that was included in 0.35.1, see #8536 . However, that particular PR focused on all other areas of Superset except SqlLab. I can look into this in the coming days.
This does appear to be a regression, not sure when it was introduced. I need to think about how to resolve this, as there are many potential solutions. Also, the url_params feature needs to be more thoroughly unit tested and documented going forward.
There was a fix related to
url_paramsthat was included in0.35.1, see #8536 . However, that particular PR focused on all other areas of Superset except SqlLab. I can look into this in the coming days.
@villebro I try to do exactly (I think...) of what it's shown in the PR and it does not work. url_params in the dashboard are not being passed to the chart and then to the datasource sql.
I'm on 0.35.2
EDIT: @villebro please ignore .. I after saw the PR was applied after 0.35.2 .. thanks!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.
Most helpful comment
This does appear to be a regression, not sure when it was introduced. I need to think about how to resolve this, as there are many potential solutions. Also, the
url_paramsfeature needs to be more thoroughly unit tested and documented going forward.