Skip to main content
New Idea

Allow the ability to include/exclude nulls when creating a participant list in a journey source

Related products:None
  • September 15, 2021
  • 7 replies
  • 112 views
DannyPancratz
FMEEvangelist
Ditte
+29
  • jaymeb
  • DannyPancratz
    DannyPancratz
  • mditucci
  • FMEEvangelist
    FMEEvangelist
  • Ditte
    Ditte
  • Jurgen
    Jurgen
  • Wolfgang Hammer
    Wolfgang Hammer
  • bjoern_schulze
    bjoern_schulze
  • Erik_
    Erik_
  • Jasper
    Jasper
  • David T-Mobile
    David T-Mobile
  • Suvi Lehtovaara
    Suvi Lehtovaara
  • Paul_
    Paul_
  • Rudi
    Rudi
  • ZapierSteph
    ZapierSteph
  • LizZaps
    LizZaps
  • jessafterhours
    jessafterhours
  • Lucia Vengrinova
  • NatTho
    NatTho
  • Milla
    Milla
  • Casstastr0phee
    Casstastr0phee
  • Mark Jongeling
    Mark Jongeling
  • dandre
    dandre
  • nate2
    nate2
  • copperml
    copperml
  • Blastoise186
    Blastoise186
  • cstrange
    cstrange
  • alfonsmr
    alfonsmr
  • SmartlyGreg
    SmartlyGreg
  • beth
  • JeppePeppe
    JeppePeppe
  • Chelsea Roberts
    Chelsea Roberts
  • mmue
    mmue
  • mibrahim75
    mibrahim75

  • Contributor ⭐️⭐️⭐️
  • 20 replies

Ideally, all of the filtering capabilities that exist in Reporting can be replicated when creating a participant list for a program.  Please see screenshots. 

 

Here’s my situation:

I have created a process for the CS team to launch a CSAT program by simply closing a CTA in a playbook.  One of their initial steps is to confirm who will receive the survey based on various roles - and this confirmation happens by looking at a report that mirrors the filters found on the journey orchestrator to identify the expected participants.  We recently identified the need to allow CSMs to exclude people from certain standard communication campaigns and would like to do this by having an “exclude” multi-picklist on the person or company person record (I’ve tested both).  

 

While I can create the proper filtering logic in the report the team uses to confirm intended recipients, I cannot recreate that filter logic when creating the sources in the program because I cannot include nulls.  The checkbox to include/exclude nulls is missing.  

 

I’m actively working on a work around and there are probably many different ways to achieve what I’m trying to do, but I wanted to let you know of the hiccup on functionality I would have expected to be consistent and available across similar areas of the platform.

 

Forum|alt.badge.img
  • Contributor ⭐️⭐️⭐️
  • September 15, 2021

And I’m hitting a wall with figuring out a workaround.  Anyone reading this who has ideas or advice, please share.  


Forum|alt.badge.img
  • Contributor ⭐️⭐️⭐️
  • September 16, 2021

I have a great conversation going in the admin community with many folks trying to troubleshoot this with me.  https://globalgainsightadmins.slack.com/archives/C01H3GB97PX/p1631747006317600


dan_wiegert
Forum|alt.badge.img+3
  • Gainsight Employee ⭐️⭐️
  • September 17, 2021

This looks like an enhancement request  - The rules engine does NOT expose an = operator on a multi-select picklist, and because of that, it is not providing the option to filter for null values that exist on a multi-selected picklist field. This seems like a product gap. Is there a backend tenant option that would enable null filtering on multi-select picklists for the rules engine -- could there be? 

 

Here’s a video comparison  of a company person report with the multi-select picklist field → the ability to include or exclude nulls IS present, then in Cynthia’s program you can only check values on the multi-select picklist. 


jordan_cook
Forum|alt.badge.img+2
  • Contributor ⭐️⭐️⭐️⭐️
  • September 17, 2021

Thanks for getting this posted!

Would be great if we could check for NULL values in a multi-select picklist in both the Rules Engine, and in JO query builder.


PavanCh
Forum|alt.badge.img
  • Gainsight Employee ⭐️
  • October 14, 2021

hi @cynthiam ,

Thanks for posting this. I have added this as an enhancement request to the product backlog for prioritisation. 


Forum|alt.badge.img
  • Contributor ⭐️⭐️
  • June 21, 2023

Upvoting, as I’ve run into the same limitation in Journey Orchestrator.


Forum|alt.badge.img+1
  • Contributor ⭐️⭐️⭐️⭐️
  • June 11, 2024

This - but now we also need it for the new JO builder.



Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings