GitHub user dosubot[bot] added a comment to the discussion: Any way to navigate from Dashboard A to Dashboard B other than Markdown in Superset 6.0.0?
<!-- Answer --> There's no built-in "share filter state across dashboards" feature in Superset, but here's what I found about how the mechanisms work and what your options are: **Why `native_filters_key` won't work cross-dashboard:** The key is scoped to a specific dashboard — the cache lookup uses `cache_key(resource_id, key)` where `resource_id` is the dashboard ID [[1]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/dashboard/filter_state/get.py#L34-L41). So the same key on Dashboard A and Dashboard B would reference different (or non-existent) entries. The Permalink API is similarly dashboard-bound [[2]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/dashboard/permalink/create.py#L70). **Your best option: the `native_filters` URL parameter (rison-encoded)** Superset still supports a `native_filters` URL parameter that encodes filter state directly in the URL [[3]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/constants.ts#L39-L42). When Dashboard B loads with this parameter, it decodes the rison and applies it as the dataMask [[4]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/dashboard/containers/DashboardPage.tsx#L162). This is portable between dashboards because it's not tied to server-side storage. **The key requirement:** The native filter IDs must match between Dashboard A and Dashboard B. If both dashboards define the same filters (e.g., `userid`, `region`) and those filters have the **same filter component IDs**, then a rison-encoded URL parameter from Dashboard A will apply correctly on Dashboard B. **Practical approach:** 1. In your Markdown link on Dashboard A, construct the Dashboard B URL with `?native_filters=<rison_encoded_state>` 2. The rison value should encode the dataMask object with filter values keyed by filter ID However, there's a catch — this requires either: - Manually ensuring filter IDs match (e.g., by editing dashboard JSON metadata to align filter UUIDs), or - Building a small middleware/script that reads Dashboard A's current filter state and maps it to Dashboard B's filter IDs **Alternative API-based approach:** 1. Read filter state from Dashboard A via `GET /api/v1/dashboard/{A_id}/filter_state/{key}` [[5]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/dashboards/filter_state/api.py#L49-L316) 2. Create a new filter state entry for Dashboard B via `POST /api/v1/dashboard/{B_id}/filter_state` 3. Use the returned key in your Dashboard B URL as `?native_filters_key=<new_key>` This requires custom programmatic logic but gives you clean URLs. **Bottom line:** Superset doesn't natively propagate filter state across dashboards automatically. The `native_filters` rison parameter is the closest thing to a portable solution, but it requires matching filter IDs between dashboards. If your filters have different IDs (which is the default when created independently), you'd need to either align them manually or build a mapping layer. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).* --- Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset). [](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=ff0c1451-9934-4a4f-bc7d-3e895011e110) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset) GitHub link: https://github.com/apache/superset/discussions/40514#discussioncomment-17131439 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
