GitHub user quyentran-23 created a discussion: How to properly design Drill 
Down and Drill Through workflows in Apache Superset?

In Superset, I see several related mechanisms that can partially cover drill 
interactions:
- `DRILL_BY` feature (right-click → drill by another dimension)
- Drill to detail (raw records view)
- Dashboard-to-dashboard navigation using URL parameters / native filters
- Jinja-based SQL templating for contextual filtering

However, compared to other BI tools (e.g. Power BI, Tableau), these feel more 
like **building blocks** rather than first-class Drill Down / Drill Through 
features.

### Questions

1. **How can Drill Down and Drill Through be implemented in Superset in a way 
that is comparable to other BI tools?**
   - From a conceptual standpoint, how should users think about replicating 
classic BI drill patterns using Superset features?
   - Is `DRILL_BY` intended to be the primary equivalent of “drill down”, or is 
it more of an ad-hoc exploration tool?

2. **What is the recommended approach for Drill Through–style workflows?**
   - Is dashboard-to-dashboard navigation with native filters and URL 
parameters the preferred pattern?
   - Are there examples or references of production-grade Superset deployments 
using this approach successfully?

3. **What best practices help make drill workflows intuitive and scalable?**
   - How many drill levels are typically reasonable before UX becomes confusing?
   - How should datasets, dimensions, and filters be modeled to support 
consistent drill behavior?

4. **Are there any known limitations or future plans related to drill 
interactions?**
   - Any discussions or roadmaps around more explicit Drill Through UX?
   - Performance, security, or permission-related considerations to be aware of?

I’d really appreciate insights from maintainers or experienced Superset users 
on how they design drill down and drill through experiences in real-world 
Superset deployments.


GitHub link: https://github.com/apache/superset/discussions/37095

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