Hi Sebastian, It is nice to hear how important is Superset for your project. There is a whole filter refactoring, details are in SIP-49 <https://github.com/apache/incubator-superset/issues/10285>. The development is happening as we speak, feel free to comment, and add feedback to the SIP. Until the implementation of SIP-49 is completed, as a workaround, you could add 2 filter boxes and cascade the input of one to the other. I did a small demo <https://docs.preset.io/docs/small-demos#how-to-cascade-filters-values>, as this has been asked several times, will this work for you? Eugenia
On Mon, Sep 14, 2020 at 1:52 PM Sebastian Brudziński < [email protected]> wrote: > Hello, Superset community! > > I'm representing the OpenLMIS community (https://openlmis.org/). OpenLMIS > is an e-health logistics management system that allows tracking commodity > levels and supports re-ordering in a way that helps reduce waste and > prevent stockouts. Superset plays an important role in our stack since the > visualization of stock data to key users helps them analyze it from > multiple angles and make better stocking decisions. > > We have recently launched OpenLMIS in Cameroon, and it turns out that one > of the most pressing issues they have with the system is not being able to > use cascading filters with Superset reports (e.g. select a district filter, > and limit facilities filter to those facilities that are within the > selected district. The best to our knowledge, this is currently not > possible with Superset. > > We've found a few issues on GitHub that seem to be related to this feature > request: > - https://github.com/apache/incubator-superset/issues/10013 > - https://github.com/apache/incubator-superset/issues/10688 > - https://github.com/apache/incubator-superset/issues/10285 > > but unfortunately, it doesn't seem like we are seeing any of the above > soon. The best estimate I've seen is from the last link, and it mentions > 1-2 years, which obviously doesn't work for us. > > Considering the above, I wonder if you have any suggestions or possible > workarounds for our scenario. Perhaps we are missing something obvious and > we could use cascading filters in a way I described? If not, are there any > workarounds? Perhaps anything we could do on our side to speed up the > feature request? > > Thank you, > Sebastian > -- Eugenia Moreno <https://www.linkedin.com/in/eugeniamorenozerdan> *Customer Engagement* *Preset.io* <http://preset.io/> Book Time with me <https://meetings.hubspot.com/eugenia5> C: 617-633-7641
