What you have described above is actually not a bug. The default filter is just a fallback filter. It is not forced in any way, and so when you apply another filter in a view, whether from the filters menu or a quick filter, the default filter is ignored. That's by design. I missed the 'default filter' in your post and thought that you meant the case where a view was set to force a filter (which is how I rephrased to title of the tracker issue). Now refining a filtered view is an important requirement and the tracker issue will address that functionality.
Re: Can a Filter's result be further refined on the fly? (Dataform Limitation)
by Itamar Tzadok -
Number of replies: 0