Salesforce Data Event related object filter criteria can truncate custom relationships
Last updated 2019-02-28 ·Reference W-5784559 ·Reported By 1 users
When nesting a custom relationship field inside an OR condition, the path, such as cases__r, will be truncated.
-Create a new journey, give it a name
-Drag SF Data Event onto the canvas
-Select an object that has a custom lookup field
-Select when the object is created only, next
-There should be a relationship field like cases__r, select this
-Select any field and add it three times
-On the right side of the filter canvas, make the bottom two criteria a nested OR condition
-In the summary, note it is already truncated like below
Cases__r:Case:AccountId EQUALS "" AND Case:AccountId EQUALS "" OR Case:AccountId EQUALS ""
This is cosmetic only and has no impact on performance or functionality. To avoid confusion, document what relationship is used in the description of the Journey itself so that other users know what relationship is used.
Reported By (1)
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.