TechAuditBI commented on PR #23216: URL: https://github.com/apache/superset/pull/23216#issuecomment-1494234195
> Hi @TechAuditBI ! I believe that the json metadata (in dashboard properties) can be used to cross filter control scoping for the time being. > > Would you be willing to share a bit more about your use case and how you're planning to use the cross filter scoping? Thanks in advance for the additional context! Hi! We are mostly using it in situations where we have a bunch of different datasets in one dashboard to cross-filter charts using identically named columns. Usually it is helpful to create separate datasets for filtering in case of working with large amounts of data so that superset does not have to run select distinct queries to get all possible options. It speeds up dashboard loading process. Also we've developed some custom charts which tend to "mimic" filter box functionality via cross-filtering e.g. time filter in a form of slider aspired by such in PBI. And scoping is crucial for it's functionality. All in all i understand that our custom charts should not be a concern for the community. But scoping feature was very useful in a regular dashboard development. If it requires some effort to support scoping in this repository, we are ready to take this responsibility. You may have seen some PRs from @Always-prog he is our developer so we have already commited some of our work t o the community and ready to expand our contribution! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
