GitHub user dosubot[bot] added a comment to the discussion: Navigation from 
table row to tab or dashboard based on row content

<!-- Greeting -->
Hello @levzatz! I'm [Dosu](https://dosu.dev), a bot here to help you solve 
bugs, answer questions, and assist you in becoming a contributor. I'm here 
while you wait for a human maintainer. How can I assist you today?

<!-- Answer -->
I found a similar unsolved discussion regarding redirecting to specific charts 
when filters are applied, which might be relevant to your query. You can check 
it out [here](https://github.com/apache/superset/discussions/23620) 
<sup>[[1]](https://github.com/apache/superset/discussions/23620)</sup>.

Regarding your questions:

1. **Navigating between tabs within a dashboard via a generated link:** 
Currently, there is no specific documentation or examples available in the 
repository about deep linking to specific tabs within a dashboard. The existing 
capabilities for intra-dashboard navigation primarily involve using nested tabs 
and native filters 
<sup>[[2]](https://github.com/apache/superset/blob/master/superset/examples/tabbed_dashboard.py)</sup><sup>[[3]](https://github.com/apache/superset/blob/master/RELEASING/release-notes-1-1/README.md)</sup>.

2. **Linking to type-specific dashboards:** Since deep linking to specific tabs 
isn't well-documented, linking to type-specific dashboards using calculated 
column links with RISON in the URL might be a more reliable approach. This 
method is already working well for you, and it aligns with Superset's current 
capabilities.

3. **Roadmap features related to intra-dashboard navigation or deep linking to 
tabs:** There is no available information on upcoming features or roadmap items 
specifically related to intra-dashboard navigation or deep linking to tabs in 
the repository.

If you have successfully implemented calculated column links with RISON for 
dashboard navigation, continuing with this approach seems to be the best 
practice given the current capabilities of Superset.


<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*

---
<sup>Help Dosu learn! Give it feedback: [Great 
Response](https://app.dosu.dev/response-feedback/297f5a13-819c-41be-9b10-07891ec37eff?feedback_type=great_response)
 | [Irrelevant 
Answer](https://app.dosu.dev/response-feedback/297f5a13-819c-41be-9b10-07891ec37eff?feedback_type=irrelevant_answer)
 | [Incorrect 
Sources](https://app.dosu.dev/response-feedback/297f5a13-819c-41be-9b10-07891ec37eff?feedback_type=incorrect_sources)
 | [Too 
Verbose](https://app.dosu.dev/response-feedback/297f5a13-819c-41be-9b10-07891ec37eff?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/297f5a13-819c-41be-9b10-07891ec37eff?feedback_type=hallucination)
 | [Bug 
Report](https://app.dosu.dev/response-feedback/297f5a13-819c-41be-9b10-07891ec37eff?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/297f5a13-819c-41be-9b10-07891ec37eff?feedback_type=other)</sup>


GitHub link: 
https://github.com/apache/superset/discussions/33405#discussioncomment-13106857

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

Reply via email to