Decision Split fails validation when second expression uses clause from first expression
Last updated 2021-05-19 ·Reference W-8533492 ·Reported By 6 users
It is possible to configure a decision split in Journey Builder that will fail validation resulting in "There is no Attribute with FullyQualifiedName" errors in the User Interface. If the conditions used in the Decision Split are flipped or if the order of Journey/Contact data that is evaluated in attribute to attribute comparison are switched, the error does not occur.
-Create a new Journey from Journey Builder
-Drag a data extension entry event onto the canvas and configure, choose DE and specify no entry criteria
-Drag a decision split to the canvas
-Add Contact Data as the top expression where a boolean condition is checked
-Drag over another field from the same DE, check to use attribute to attribute comparison
-Navigate to Journey data and add an attribute to the attribute to attribute comparison in above expression
-Save split. Click validate on the Canvas.
-Observe error in validation.
-Flip the condition so that attribute to attribute comparison is evaluated before the boolean condition
-Configure the attribute to attribute comparison expression so Journey data is evaluated on the left hand side instead of the right
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.