Hi!
I saw today something that wasn't happening before.
I want to send a public link with the query param indicating the tab, and for some reason the dashboard is always defaulting to the first tab.
Example:
When I open this link
https://mymb.metabase.com/public/dashboard/uuid?tab=12-secondtab
It navigates to
https://mymb.metabase.com/public/dashboard/uuid?tab=11-firsttab
Is there any solution for this?
Thanks,
Facundo.
@Luiggi can you please confirm if this is a bug or not? It's a new behavior that has been reclaimed by our customers.
Thanks!
TonyC
April 18, 2024, 12:09pm
3
Upgrade to 1.49.6 since that should be fixed
@TonyC we are currently using Metabase Cloud, Enterprise version. I read in the documentation that minor updates should been done automatically. Is there anyway way for accelerating this?
We are currently in version 1.49.5
Thanks.
TonyC
April 18, 2024, 1:00pm
6
It's this one:
opened 07:30PM - 15 Apr 24 UTC
closed 09:28AM - 16 Apr 24 UTC
Type:Bug
Priority:P1
.Frontend
Embedding/Signed
.Team/Embedding
### Describe the bug
Hello everyone 👋
We've noticed that in the latest versio… n (v0.49.5) the `URL?tab=tab_id` is not applied when embedding a dashboard in an iframe.
In our case we have `https://URL?tab=2-tab-2` but the iframe renders the tab with id `1-tab-1`
### Screenshot:
<img width="1517" alt="Screenshot 2024-04-15 at 22 18 35" src="https://github.com/metabase/metabase/assets/24255041/712f5726-e333-4f2f-b59a-bd698fa42469">
### To Reproduce
1. Create a dashboard with more than one tabs
2. Enable embedding for that dashboard
3. Create an embedding URL and defined a tab other than the first in the url of the embedded dashboard by appending ?tab="TAB_ID" in the url
4. Expect the embed to open the tab with id "TAB_ID:
5. The embed loads the default tab (first one)
### Expected behavior
It should render the url defined tab like it did in previous versions
### Logs
_No response_
### Information about your Metabase installation
```JSON
- Browser: Google Chrome Version 123.0.6312.123 (Official Build) (arm64)
- OS: Macos 14.4.1 Sonoma
- DB: PostgreSQL
- Metabase instance: self-hosted but happens on the cloud instance too
- Metabase version: `v0.49.5`
```
### Severity
High - blocks multiple users
### Additional context
_No response_
Reach out to help@metabase.com and mention the instance name on the email ... They are done automatically but they take a couple of days