as i found out here: Use case 1 to many relationship in Contact Builder
If Data extensions are linked in Contact Builder via one to many relationship it is not possible to use the DE in a Decision split in Journey Builder.
If i remove the One to Many relationship in Contact Builder i am not able to use this Data Extension in the Decision Split in Journey builder. Here comes the problem:
It is quiet similar / same problem as discussed in link. Lets say i have following entries in the Data Extension which i want to use for filtering with the Decision Split:
> Id,Product > 0031N00001IyHRiQAN,Banana > 0031N00001IyHRiQAN,Apple > 0031N00001IyHRiQAN,Carrot
No i would like to have the subscriber to enter the decision split Path accordingly.
The 1 to many relationship in Data Model is because the Journey tracking data needs to be synced to the contact in SF.
is there any better best practice or workaround then:
A. Query each product in a dedicated Apple, Banana and Carrot Data Extension and use those from query created Data Extensions for the decision splits?
B. Create a query which pulls always the most recent record only and save it to a NEW Data extension which will be used as entry criteria every time a new record is added.
I hope you get what i try to say.