Attribute-to-Attribute comparison does NOT resolve filters correctly on JB decision splits
Last updated 12 days ago ·Reference W-7469528 ·Reported By 17 users
We have identified that the journey builder is not evaluating our records correctly when we have a nested AND/OR split specifically when we use attribute-to-attribute comparison. When we use attribute-to-attribute comparison, only the top statement is evaluated.
Steps: If we set a decision split as mentioned below
(Attribute from contact data === Attribute from Journey data) AND
((Value of contact data is null) OR (Value of contact data is False))
However, when using the only attribute to attribute comparison, the contact is taking the correct path.
Use multiple decision splits instead of nested conditions.
Is it Fixed?
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.