Journey Builder Filters using Attribute to Attribute comparison where one attribute is compared to more than one other attribute fail
Last updated 2020-08-31 ·Reference W-5457570 ·Reported By 0 users
Journey Builder filters (decision split, goal or exit criteria) can be created where the same field from the event source data extension is compared to two different attributes using attribute to attribute comparison, but when attempting to evaluate the filter the contact will error out of the Journey.
1) Create a data extension named "BreakAtoATestEvent"
2) Create three fields for the DE created in step 1, "SubscriberKey" (Text data type), "EmailAddress" (EmailAddress data type), "DateParameterEvent" (Date data type)
3) Create a second data extension named "BreakAtoATestDecision"
4) Create four fields for the DE created in step 3, "SubscriberKey" (Text data type), "EmailAddress" (EmailAddress data type), "DateParameterDec1" (Date data type), "DateParameterDec2" (Date data type)
5) Add rows to your two DEs for Contacts that already exist on the All Subs list (so you don't have injection issues), be sure the same SubscriberKey value is supplied to both DEs and put the current date in for the date fields (you can really put any date you want in here)
6) In Contact Builder, create an Attribute Group named "BreakAtoA"
7) Link the data extension "BreakAtoATestDecision" to Contacts on "Contact Key" equals "SubscriberKey"
8) Create a Journey named "BreakAtoATest"
9) Drag an Event onto the canvas
10) Click Configure > New Event > Contact Data > Next > name it "BreakAtoATest" > select your "BreakAtoATestEvent" data extension > Next > Next > Next > Done
11) Drag a Decision Split onto the canvas
12) Click Configure > Create Filter Expression > Click "Contact Data" > Click "BreakAtoATestDecision"
13) Drag over "DateParameterDec1" > Click to go back to Event Data and drag over "DateParameterEvent" for attribute to attribute comparison
14) Go back to "Contact Data" > Click "BreakAtoATestDecision"
15) Drag over "DateParameterDec2" to create a second condition > Click to go back to Event Data and drag over "DateParameterEvent" for attribute to attribute comparison
**NOTE: This is the piece that causes the error, comparing two different data extension fields to the same Event Data Attribute
16) Click Next > Done
17) Click Settings for the Journey and set the entry mode to Re-Enter Anytime
18) Activate the Journey
19) Go to Automation Studio > Create Automation > Name it "BreakAtoATest" > Drag over a Fire Event > Click Choose > Select "BreakAtoATestEvent" > Done
20) Save the automation and click Run Once
Create a second data extension field on the Entry Source Data Extension populated with the same data as the first. Use this second field for comparison rather than comparing the same field twice.
Reported By (0)
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.