Loading

Decision Split with filter operator 'Is Null' for all attributes, sends contacts to path 1 even when there are no records present on linked data extensions in Contact Data path

Publiseringsdato: Jan 28, 2025
Beskrivelse
Within a Journey Builder Decision Split filter, if we have a filter logic as follows:

FirstName is null

(Where 'FirstName' is an attribute selected from a Data Extension linked in the Contact Data path)

Now usually, if a record isn't present corresponding to the contact key for which 'FirstName' is to be evaluated, the contact would go down the remainder path. So for example, if we have a filter logic as follows:

FirstName equal John

And if a record isn't present corresponding to the contact key for which 'FirstName' is to be evaluated, the contact will go down the remainder path because of the absence of record on the Contact Data path.

But for the case, where the filter uses 'Is Null' operator for all the attributes, even when there exists no record on the Contact Data path, the filter criteria is evaluated 'True' and contact is sent to path 1.

This is because the absence of record on the Contact Data path would cause the filter 'Is Null' to be evaluated to 'True'. The filter would be evaluated to see if the attribute's value is null or not, and when there’s no record on the Contact Data path, null values would be returned, satisfying the filter criteria.

In order to evaluate the decision split filter criteria, a select query is executed to check the data. This query will join all objects necessary, which also means no record will return as Null.

This behavior is only observed when all the attributes in the filter have the 'Is Null' operator being used.
Løsning
The workaround is simply to add one more filter criteria using the operator 'Is Not Null' to a required field on the same Contact Data path data extension.

For Example, if there’s an attribute 'Id' present on the same Contact Data path data extension where the 'FirstName' attribute is selected from, then add a filter as follows:

Id is not null

This additional filter would evaluate if the data exists in the data extension from where the FirstName attribute has been selected. If data exists and has a Null value for FirstName, the contact will go to path 1, else will go down the remainder path.
Knowledge-artikkelnummer

000396692

 
Laster
Salesforce Help | Article