Subsequent new filter selections are not taken into account while the data retrieval from the previous selection is still executing
This feedback comes from one of our external clients who has been testing the ABS tented Data Explorer. This client found there was a significant delay in loading every single time a new filter was selected. This impacted usability and let to a bug where sometimes DE would say "no data" even though data existed for the query. The test datasets loaded in the tenanted deploy are not especially large.
This is not top priority for ABS but important for the long-term usability on DE.
After selecting filters, the data did not show, even though I was looking for some very simple query. I did the same filter again, but slower, step by step, waiting for the page to load before selecting new filter, and this time it worked. I’m not sure what the problem was there.
The following feedback is not a bug but an independent enhancement idea and would need another ticket (to be prioritised):
There should be a button ‘apply filter’ rather than updating on the spot when user selects the filter. It may be good for a user selecting a few data data points, but in many cases we are looking at a huge amount of data, it takes a lot of unnecessary loading time every time we select a new filter.
This enhancement idea is independent from the actual bug reported, because even with an "Apply" button, this bug can still happen: After having clicked on the "Apply" button and when making a subsequent new filter selection, using the "Apply" button again could fail if the previous data retrieval action is not yet completed.