Not able to take URL_PARAM in explore chart
See original GitHub issueA clear and concise description of what the bug is.
How to reproduce the bug
- Go to ‘http://localhost:8088/superset/sqllab/?name=can_read’
- Write query on default dataset on sqllab ‘select * from ab_permission where name = ‘{{ url_param(‘name’) }}’’
- Click on explore after running the query (it should return one row)
- click on explore.
- now write &name=can_read in the URL.
Expected results
URL parameters should persist in the URL and should be read by charts
Actual results
URL parameters disappear
Screenshots
URL params working in SQL lab

URL param disappears from url

Environment
(please complete the following information):
- browser type and version: persists on all browser (chrome ,Mozilla,brave)
- superset version:
[2.0.0](https://github.com/apache/superset/releases/tag/2.0.0)
Additional context
I am using jinja templating and I am using URL parms to get the data. I have change feature flag as well still it is not working.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6
Top Results From Across the Web
c# - Url parameter not mapping - Stack Overflow
Unfortunately my parameter doesn't map correctly and it is always null . UPDATE Additional information: here is my RouteConfig class: public ...
Read more >Superset / Preset Jinja URL parameters - YouTube
This video is a demo about how to change the dataset to take URL parameters to present filtered data in a dashboard.
Read more >URL query parameters - Retool Docs
You can use URL parameters to share a link to the app with a specific user already populated. Users and purchases tables. To...
Read more >How to get URL Parameters using JavaScript ? - GeeksforGeeks
In this article, we will learn how to get the URL parameters in Javascript, along with understanding their implementation through the examples.
Read more >Parameters - Looker Studio Help - Google Help
You can also use parameters to create report templates. ... For example, an account number parameter, or name of a database table would...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@YiouZuo The problem is with the docker image. The latest docker image is breaking. I resolved the issue by making changes in the docker-compose. and moved back to the previous version. In docker-compose make changes
x-superset-image: &superset-image apache/superset:${TAG:-latest-dev}Tox-superset-image: &superset-image apache/superset:44c5e2879b912b33c902b955eebdaa52ea6e5354this id I got from an older version of the docker image from the official docker.@syedgufran95 Thank you for your suggestion! One caveat of rolling back to an older image is that some of the newer functions are lost – one that matters in my case is the ability to save datasets from sqllab. I’ll just need to wait until Superset fix their bug 😦.