Skip to main content
kelly
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

    heather_hansen
    heather_hansen
    VIP ⭐️⭐️⭐️⭐️⭐️
    March 4, 2021

    Agree with @kelly.  You can work around it, but it would be simpler if the workaround wasn’t needed. 

      gunjanm
      gunjanm
      Expert ⭐️
      March 4, 2021

      Agree with @kelly.  You can work around it, but it would be simpler if the workaround wasn’t needed. 

      This!

      Gunjan
        darkknight
        darkknight
        Expert ⭐️
        March 4, 2021

        100% 

        Jeff Kirkpatrick
          jenlpro
          jenlpro
          Helper ⭐️
          July 7, 2022

          I am finding that I can’t even really work around this issue! In Rules Engine, I tried to use a filter where my field excluded all available values, meaning that in theory NULL records would appear…. but they still don’t 😭 I have over 4500 records that need updating and I can’t use Rules Engine to do it so now I’m back to the drawing board 🙃

          tippetts
          tippetts
          Contributor ⭐️⭐️⭐️
          July 20, 2022

          Same. Currently in Rules engine, I can’t seem to get a decent workaround. Are there plans to update this in the future to allow filtering on null multi-select fields? 

          darkknight
          darkknight
          Expert ⭐️
          July 21, 2022

          @anirbandutta may we get this converted to an idea? Thx!

          Jeff Kirkpatrick
            anirbandutta
            anirbandutta
            Expert ⭐️
            July 21, 2022

            @darkknight would this Idea be the same?

             

            It's an opportunity for engagement
            kelly
            kellyAuthor
            Helper ⭐️⭐️⭐️
            July 21, 2022

            @darkknight would this Idea be the same?

             

            @anirbandutta  I don’t think that is the same, that post is asking for the null box so you can include or exclude null values. 

             

            This post is describing how the system does not consider null values at all in the include/exclude filter. For example if I want to exclude values B, C, and D, theoretically I should get back A and Null, but I only get back A. 

              matthew_lind
              matthew_lind
              VIP ⭐️⭐️⭐️⭐️⭐️
              July 21, 2022

              First, I’m 100% behind native functionality to query for records where a multi-select dropdown has no values selected.

              Second, until that’s available, a potential work-around for those needing it:

              1. On the object in question, create a new field with Type of String.
              2. In the Rules Engine, build a rule to regularly populate/update the new String field with the values of the multi-select dropdown.
                • In the rules engine, you can map a multi-select dropdown to a String field, and the values in the String field will be a semi-colon-separated concatenation of the multi-select dropdown values.
              3. Now you can use the new String field in your queries, where you can then use filters that incorporate the null values.
              Making people their best....currently disguised as a CS Ops Architect. How can I contribute to your success?
                bradley
                bradley
                Expert ⭐️
                July 21, 2022

                @darkknight would this Idea be the same?

                 

                @anirbandutta  I don’t think that is the same, that post is asking for the null box so you can include or exclude null values. 

                 

                This post is describing how the system does not consider null values at all in the include/exclude filter. For example if I want to exclude values B, C, and D, theoretically I should get back A and Null, but I only get back A. 

                Yea, this is a massive bummer for any data type in Gainsight to be honest. Even for a boolean field where you say “does not equal yes/true” you’d think your query would find anything matching that, which would be No/false and null, but instead there’s an extra step and is a pretty big gotcha.

                  Show more replies
                  Terms & ConditionsAccessibility statement