Jump To Dashboard add-in
It lists dashboards with the _drill_ prefix. It lists only dashboards using the same datasource.
I have a drill-down dashboard that uses two datasources: one that matches my parent dashboard, and one that shows more granular information. I'd like this drill-down dashboard to appear on the JTD list. I think the JTD list should show any dashboards that share at least one datasource with the parent.
Thanks Yuliya, that seems to be exactly what I was looking for.
For anyone else looking at this, the configuration file is:
/opt/sisense/storage/plugins/jumpToDashboard/js/config.js
Hi Tim,
In order to display all dashboards with _drill_ prefix (regardless of their datasource) in the JTD list, an administrator can set sameCubeRestriction parameter to false in the JTD global configuration.
Furthermore, starting from Sisense version L2025.1 SP1, the JTD can be configured in the widget UI. In addition to choosing the target dashboard from the '_drill_' list, the configuration settings include an option to select any dashboard by ID.
You can find more details in the Configuring JTD Per Widget documentation.
I hope you will find it helpful for your specific use-case.
Hi Tim ,
Thank you for your valuable product feedback.
The reason dashboards that don’t match the parent dashboard’s datasource aren’t appearing for you is due to how the drill-down (JTD) works. The main reason is that the drilled dashboard inherits the parent filters and applies them to the drilled dashboard, which could cause issues if the datasources don’t align.
That said, there is a FREE marketplace plugin called Advanced Jump to Dashboard. Its primary purpose is to simplify JTD configuration by exposing all parameters through an easy-to-use UI. However, it offers more functionality. With this plugin, you can easily select the dashboard you want to drill into and choose which filters to pass to the drilled dashboard directly from the UI.
Additionally, you can save JTD settings as presets and reuse them in other dashboards, so you won’t need to configure them from scratch each time.
This plugin also offers more capabilities when combined with other plugins. Feel free to reach out to inquiries@paldi.solutions to get this plugin today.
Paldi Solutions - Number #1 Sisense Plugins Developer
Hi Benji,
"issues if the datasources don’t align" - that makes sense, but my typical use case is to have a summary dashboard that can jump to a more granular dashboard. The granular dashboard shares the summary cube, but also uses a more granular cube. I'm not saying the list should include all target dashboards, just the ones with some overlapping cubes. Or just dashboards that use all cubes that the parent dashboards uses.
"Advanced Jump to Dashboard" - If I use this in a dashboard, and then import that dashboard onto a Sisense server that doesn't have AJTD, does the dashboard keep my JTD settings?
(Currently, we often set up JTD using javascript. Sounds like AJTD is basically a UI for that. That'd be more user-friendly for us. But we need to be able to push dashboards out to multiple clients, and I'd like AJTD to be optional rather than necessary.)
We push dashboards to multiple clients, and we have a development environment that sometimes has several copies of the same dashboard. Is that going to make the choose-the-target-dashboard dropdown confusing? Can I still go into the dashboard's javascript events and overwrite the target with an ID? If I import dashboards on a new server, does JTD/AJTD 'remember' the target by name or ID? I suspect we'll have to manually re-select the target each time we push/import a dashboard, but that's already the case anyway.
Hi Tim ,
As for your question about Advanced Jump to Dashboard (AJTD), you're correct – it simplifies JTD configuration through a UI, much like how you’re handling it programmatically with JavaScript. However, if you import a dashboard onto a Sisense server without AJTD, the JTD settings won’t persist unless the plugin is installed in the target environment.
You can still modify the dashboard’s JavaScript events to overwrite the target with an ID, providing more precise control in your specific use cases. Unfortunately, the current free version of AJTD doesn't track targets by name or ID across environments, so you’d need to manually re-select the target when pushing or importing dashboards – much like your current process.
It sounds like AJTD might not fully address your needs given your programmatic workflow. That said, we have considerable experience with Sisense customizations for specific use cases. If you're interested, feel free to reach out to inquiries@paldi.solutions, and one of our experts will gladly assist with a tailored solution.
