Skip to main content
kelly
Helper ⭐️⭐️⭐️
March 4, 2021
New Idea

Why Aren't Null Values Considered When Filtering 'Excludes' in a Multi-Picklist field?

  • March 4, 2021
  • 30 replies
  • 766 views

If I filter on a multipicklist field in my program by doing ‘Excludes’ and select the values that I want to be excluded from the query, you’d think that would bring in any account that doesn’t have the excluded value.

But after troubleshooting why certain accounts weren’t meeting my criteria I realized that it was due to their field value being null. Essentially if you are filtering a multipicklist field, it limits the audience to only the accounts that have a value in that field and any account with a null is not considered in the filter logic. 

You’d think by definition an account with a null value meets the criteria because it does not have the excluded value. This is not at all intuitive to a user.

 

Adding the screenshot from similar idea and merging the Idea

Hi.

Currently, we don’t have an option to choose/select the “Include Null Values” for the Multi-Select Picklist fields in Rules and/or JO Query Builder.

When ever we drag the multi select picklist field in to a filter section (Ex: in Rules) we have to choose either Includes or Excludes option only and unable to select the “Include Null Values” as well. Like how we have this option for Picklist Data type fields.

Screenshots for the same:

 

Due to unavailable of this option we are unable to get the Null value rec

30 replies

Contributor ⭐️⭐️⭐️⭐️
January 30, 2023

Still the inconsistency between rules and reports, which are supposed to be both Horizon, remains. This creates so much tech-debt for admins to clean.

bradley
Expert ⭐️
January 30, 2023

Still the inconsistency between rules and reports, which are supposed to be both Horizon, remains. This creates so much tech-debt for admins to clean.

Agree things are and will still be a bit disjointed in some places, just wanted to highlight an upcoming change and give credit where credit is due :)

The whole ‘null’s thing in general is still a PITA either way

anirbandutta
Expert ⭐️
February 20, 2023
No Status→Acknowledged
It's an opportunity for engagement
anirbandutta
Expert ⭐️
February 20, 2023
Updated idea statusNo Status→Acknowledged
It's an opportunity for engagement
anirbandutta
Expert ⭐️
February 20, 2023
The following idea has been merged into this idea:

All the votes have been transferred into this idea.
It's an opportunity for engagement
anirbandutta
Expert ⭐️
February 20, 2023
Acknowledged→Under Consideration
It's an opportunity for engagement
anirbandutta
Expert ⭐️
February 20, 2023
Updated idea statusAcknowledged→Under Consideration
It's an opportunity for engagement
sacha
Contributor ⭐️⭐️⭐️⭐️⭐️
April 24, 2023

Bump - this is whack and pretty sure it worked as expected in SFDC version.

cmultanen
Helper ⭐️
June 9, 2023

+1, this is a huge pain and it makes multi-picklists more of a net pain than a net positive. There are already so many limitations and inconsistencies with multi-picklists in regards to reporting and updating. It makes me want to reconsider using them entirely. 

alizee
VIP ⭐️⭐️⭐️⭐️⭐️
October 30, 2024

Wouldn’t it be time to look at this? It’s such a hinderance. 

Here’s recap of what doesn’t work with multi picklists: 

The multi picklist by @respectablesoundtrack6143 | Suno

The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.