I have here a long-time issue that drives me nuts.
I need to be able to set a default filter that will always be on (the red area). So the condition after it must be an AND, not OR as is now.
Then I need to have a few optional pinned filters that take into account the data already pre-filtered by the default filter. Each one goes with the OR condition.
@mdubakov , any chance for you guys to implement this any time soon?
It looks like the first filter group (red box) contains filter criteria which are already part of the pinned quick filters.
I don’t see a reason why you need the first group at all.
Alternatively, you could have 3 AND-joined top level filters:
the two in the first group plus a Type is … filter, where you make it a quick filter with no default value.
Then users have a drop down for switching between Types
I don’t want the pinned filters to have the same criteria that’s set for the default filter. I want the pinned filter to inherit the default filtering logic automatically so I can set the additional filtering criteria on top of the default one.
The problem there is that when all pinned filters aren’t pressed/activated, I see the data I don’t want to see because I want that data to be filtered out by the default filter which in this case should not be shown at all.
My suggestion was 3 filters:
1 for the Hubspot filter (default, always on)
1 for Status is not completed (default, always on)
1 for the Type field (no value chosen, pinned as quick filter)
The non-Architect user will see a single quick filter that allows them to choose any possible Type value (without affecting the default filters)
Don’t use filter groups.
3 top level filters.
AND-joined.
The third filter is a Type is … filter (with no value selected). It is the only one pinned as a user-selectable filter (they can choose any value).