Skip to main content
phani_kumar
phani_kumar
Gainsight Employee ⭐️⭐️
February 10, 2022
New Idea

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

Related products:CS Reports
  • February 10, 2022
  • 16 replies
  • 367 views

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 records. If we can get the same option like how we have for the Picklist field would be great.

Thanks.

    16 replies

    Show previous replies
    benwanlessmenlo
    benwanlessmenlo
    Contributor ⭐️⭐️⭐️⭐️⭐️
    February 5, 2025

    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.

    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

      alizee
      alizee
      VIP ⭐️⭐️⭐️⭐️⭐️
      February 5, 2025

      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,

       

      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.
        alizee
        alizee
        VIP ⭐️⭐️⭐️⭐️⭐️
        February 5, 2025

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

        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.
        angela_domenichelli
        angela_domenichelli
        Contributor ⭐️⭐️⭐️⭐️⭐️
        February 7, 2025

        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.

        Angela Domenichelli (She/Her/Hers)
        cmultanen
        cmultanen
        Helper ⭐️
        April 10, 2025

        +1 this is a big pain point with multi-picklists. Any update? I’m sure a lot of customers would benefit from this.

        alizee
        alizee
        VIP ⭐️⭐️⭐️⭐️⭐️
        May 16, 2025

        It’s possible in reports! Why is it not everywhere else? 

        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.
        Terms & ConditionsAccessibility statement