I just noticed a major inconsistency when it comes to filtering with null values.
We filter on null values in almost all of our reports, power lists, and rules. In these cases, when I need to include a null value I select the field, select the "equals" operator, then check the box (it now has the wonderful help feature that explains what it includes or excludes, see below screenshot)
The other day I created an outreach that had several variants with filters on null values. I set up the variant filters that needed to include null values the same way I would set up the report, rule, and power list filters. The screenshot below shows how I set that up.
However, when I checked to make sure everything was running correctly, [i]I noticed that the emails were backwards. Those clients who should be receiving the variant with a null value were receiving the email that didn't have a null value and vice versa. When I flipped the operator from "equals" to "not equals", everything started working as needed.
Has anyone else noticed this?
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.

