We are an association so much of what we want to communicate is related to a parent account, not the contact specifically. As we can only go two hops on the dynamic content it is severely restricting and renders much of the data we try and pull over via Insights Sync useless. Would be great if Account was a starting context like Contact/ContentSettings or if we could do multiple relationships. I had hoped you would support nested scope so tried to use nested for-each loops but the editor threw an error: {{#each Entity.RelationshipName }} {{#each this.SecondRelationshipName }} ... {{this.RelatedField1}} ... {{this.RelatedField2}} ... {{/each}} {{/each}}
Comments
Have the same issue. 2 Hops is not sufficiant.
We need to be able to reach information from Contact-->leads-->Journey. or Lead -> Contact -> Journey.
Category: Personalization
Agree as well. Need more than two hops. Additionally, ability to retrieve data using REST API could help also to place data on body of email.
Category: Personalization
Agree - we need more than 2 hops. Accessing Lookup name values from the Account record aren't even possible at this point :(
Category: Personalization
Administrator on 2/14/2023 2:49:21 PM
In Real-time we do support upto 6 hops along with the ability to set starting point as Account (see Personalize content using pre-defined dynamic text (Dynamics 365 Marketing) | Microsoft Learn). We do not plan to support these in Outbound.
Supporting a way to bring in data via API is on our backlog.
Thanks
Product Manager, Personalization