Is it possible to provide an option to choose "Include Null Values" for Multi-Select Picklist fields

Please please please. Getting this kind of information through ‘count of’ filtered tasks and reassembling that is really a waste of the available number of tasks we can have in rules engine and JO (I know it’s going to change), not everything warrants a data design either. This is really a feature we needed yesterday.

@vmallya, @Prateek Parashar could you pl take a look at this requirement?

cc @PavanCh  

Pretty frustrating to have to work around this still today in Data Designer (and all other areas)

Heavy +1!
Working around this silly gap consumes a lot of time, would love to see this implemented in the near future!
 

+1 - Running into this with Horizon Rules as well.

What’s the easiest way that you use to work around this? (I’m filtering Relationships in Data Designer.)

Best option I can think of:

1. Fetch Relationships, including the multi-select picklist
2. Transform: Only include GSID field. Filter for picklist values in [select all items].
3. Merge: Join the filtered GSIDs back to the original list of Relationships
4. Transform: Filter for that merged-in GSID field is null, to find Relationships without anything in the multi-picklist.

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

I almost went down this path, but I tried something else. In horizon rules I was able to bring the field in and use the ‘duplicate as string’ option then use the ‘does not contain’ filter on the new string field in a later step to get the desired results.

Still this is not ideal, if the name of pick-list item is ever updated it cause unintended consequences for this rule, so maintainability it would be really nice to have the ‘is not null’/’is null’ options.

Best,

Ben Wanless

Filtering's a nightmare, nulls and not nulls,

Transforming data, it takes its toll.

Can't handle filters, it's out of control,

Multi-select pick lists, they take their toll.

Multi-select pick lists, you're a tricky game,

​@LiamGilleran As discussed, we’re many wanting this :). 

Ran into this last week and ended up changing the field to a single-select in Salesforce & Gainsight.  My other proposed work around was to create a new Boolean field for each use case and transform data in a case statement before populating.  Very messy.