Filtering by Dropdown: Include blanks with "Does not have this option selected"
Filtering based on drop-downs works well for the most part, but I keep coming into issues with this.
Currently, when filtering "{Dropdown} does have this option selected [dropdown option]", it only pulls through records where the dropdown isn't blank and has a different option than the one mentioned in the filter.
This forces the user to create a conditional group, where the option isn't selected OR the field is blank.
This isn't a big deal, until you start working with more complex filters with different conditional groups.
Really loved how this was done in Classic; with the ability to check "is/isn't any of these options", and would let blanks slide through.
Thanks!
Anonymous
shared this idea
4 comments
-
Mariya
commented
Hi Mike,
Thank you for commenting on this suggestion! At this time, to include records with blank Drop Down fields, you would need to specify 2 filter criteria: 'Does not have this option selected' and 'Has no options selected'. I went ahead and logged a feature request in your organization's name as well with our Product team for them to review and consider altering the behavior of this functionality in a future project, to include Drop Down fields with blank values in the 'Does Not Contain' filter criterion.
Once this feature is released to the system, you will be notified via email!
Kind Regards,
Mariya -
Mike Pickering
commented
(Original author of this request and any others: Please also upvote the request that is titled very similarly to this about filtering on Text fields by "Does Not Contain" which behaves in exactly this same erroneous manner).
I strongly support this request, as well as applying this same concept to filtering by text fields - "Contains" and "Does Not Contain" should cover the world of possibilities, but blanks are, for no good reason that I can fathom (since "Is Blank" is an option to find the blanks) NOT treated as "Does Not Contain".
The result is that MOST of my complex filters created to date have been incorrect and have left out numerous records for our sales efforts. And also means that every one of my complex filters now will become considerably more complex and vulnerable to error.
Again, I can't begin to think of a reason for "Does Not Contain" to behave in this way and it creates a significant basic flaw in filtering and view creation capabilities that may not be evident to users until they have already created numerous incorrect views.
I have logged a request specific to filtering by text fields for this purpose as well.
-
Matt Cox
commented
this would help filters look a lot cleaner
-
Witte
commented
Hello,
You are correct, the underlying filtering logic is one of the larger differences between our Classic and New platforms, and that is an enhancement request that we have received in the past. I have logged your comments on that request, and if you would like to reach out to support with your identity we would be happy to keep you in the loop with any changes to that functionality.
Regards,
Witte