Attribute to Attribute Comparison does not always work when Contact Data is on the Right Side
Last updated 11 days ago ·Reference W-6410681 ·Reported By 21 users
Attribute to Attribute Comparison does not always work when Contact Data is on the Right Side and there is more than one path to the Data Extension in Data Designer. For example if you have the below:
JourneyData.Field = ContactData.Field
We will use the shortest path to get to the Contact Data Data Extension. This may or may not be the path you selected when configuring the Attribute to Attribute Comparison. This could result in unexpected or unintended results wherever Attribute to Attribute Comparison is used.
-Create 3 Data Extensions ABC, DEF, GHI with required fields Subscriberkey and EmailAddress
-Add the same contact to ABC and GHI but NOT DEF
-Go to Contact Builder > Data Designer > Create New Attribute Group
-Link ContactKey to ABC.Subscriberkey
-Link ContactKey to DEF.Subscriberkey
-Link ABC.Subscriberkey to GHI.Subscriberkey
-Link DEF.Subscriberkey to GHI.Subscriberkey
-Note there are now two equal paths to GHI
-Go to Journey Builder, Create new Journey
-Configure the Entry Source to use ABC
-Complete the entry source
-Drag a decision split onto the canvas
-Select Journey Data.Subscriberkey
-Select "Add an attribute to compare"
-Select Contact Data > Your new Attribute Group > Path through ABC > Click and drag GHI.Subscriberkey
-Configure the rest of the journey
Note the results may vary as there are two equal shortest paths. In some instances the contact will go down the yes path and others it will go down the no path. Create new versions of the journey to continue testing.
Switch Journey Data to the right side and Contact Data to the left.
Otherwise, ensure that the Contact Data only has one path to it.
If using Contact Data = Contact Data, there is not currently a workaround if multiple paths exist on the right hand side Contact Data.
Reported By (21)
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.