-
Notifications
You must be signed in to change notification settings - Fork 14.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] Intra Dashboard Interaction (Publish Subscriber Design Pattern) #7512
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
@xtinec take a look! |
@xtinec , if you have any thoughts over this design we can discuss . |
@mistercrunch @graceguo-supercat ..any thoughts or input over this feature |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
Any input on when this feature scheduled for development? |
any update about this feature |
Need this feature for the execs that dont know how to investigate data on their own. They just want the intuitive "click to go deeper" approach. This sounds like a really cool design and I hope it gets picked up! |
Agreed with these comments. Lack of this feature will probably prevent adoption by my org. |
This is highly desirable.. |
We are aware of the high demand of this feature, and have been working on setting up the architecture to enable cross filtering, drill down etc. that PowerBI and other BI tools offer. |
FYI as part of the dashboard native filter project we've recently introduced a new hook to viz plugins that can be used to push data from a viz to the dashboard. For now it's mostly limited to adding filters and overriding temporal parameters (time range, time grain etc), but we're also looking into supporting other types of interaction, like changing groupbys etc. This can be used to drive cross filtering between charts and also drill downs down the road. See the |
Glad to hear!!!! |
Based on @villebro comment above, is there a timeline for when we might be able to perform drill through natively? |
is there any updates or timeline ? this feature will provide wider adoption |
Looks like there is some good progress in this PR: #14688 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Most of BI Tools have features of Data Drill Down and Dashboard Linking but superset doesn't have this in design so this is Design Proposal to add these features in superset and we can serve below use cases
Use cases
Intra Dashboard Interactivity means whenever user do selection over any visualization/chart in Dashboard then selection of that chart can apply to rest/set of charts in following manner depends on UX/Usecases-
Apply as filters/global filters in sql query as where clause with required query operators referred as applyFilter
Change model or schema of chart referred as changeConfig
Show information in popup referred as showPopup
Redirect to new URL or any other dashboard url referred as redirectToUrl
Mix of any action listed above referred as applyFilter and configChange
Selection sync or highlight same selections in different charts referred as highlightSelections
Design
To solve above use cases here is a design proposal to implement above feature in superset and calling it as Publish Subscriber Design Pattern , in this any charts which is used for selection (via click or user-interaction) called as Publisher and rest /set of charts listening these selections and update itself based on action defined called as subscribers.
refer to following terminology
Design Flow screenshot
** 2. UI for get info of publishers and subscribers from user**
Steps
1.There is a option on Dashboard to configure above parameters
2. A separate UI at dashboard level open to set PubSub info from USER and store it as PubSubMetaData .
3. once user will choose this option and it will store in Dashboard state and MetaData.
Describe alternatives you've considered
We can implement above design in two stages
Phase -I
Phase -2
Additional context
NA
If anyone have any thoughts related to this type of feature then we can have a discussion further .
The text was updated successfully, but these errors were encountered: