Decision Split comparison of non nullable attributes shows error "Nullable Fields cannot be compared. One of these two fields is nullable"
Last updated 6 days ago ·Reference W-7297559 ·Reported By 15 users
When trying to compare Journey Builder data with contact model data within a decision split in a Journey and both attributes are non Nullable, on some occasions the error below will show
"Nullable Fields cannot be compared. One of these two fields is nullable"
Add Decision Split to Journey
Chose a Contact Data Attribute
Click "Add an attribute to compare"
Chose a Journey Data attribute to compare with
At this moment there is no workaround other than comparing contact data with contact data if possible
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.