Hi Pippa,
> From the clauses in your segment, it seems that you're filtering contacts by event(event name) > event registrations(under a specific event name) > contact(lookup field),
and our dynamic expression is: contact.contact_msevtmgt_event_msevtmgt_originatingeventid.msevtmgt_name.
As far as I know, there are two methods to add a contact to an event:
1. In event portal, visitors submit registration form and a contact record will be created/updated, an associated event registration record will be created at same time.
2. CRM user adds a contact record to a specific event manually in event form, then an associated event registration record will be created.
However, by method 2, event if an event registration record will be created, but the contact's Originating event field won't be populated;
in other word, the field will be only populated when the contact record is submitted by event registration form in event portal.
(Kiyomoto Tomoki has registered an event, but its Originating event is still blank because the record had existed in CRM and I added him to an event manually)
> You issue might be caused by reason below:
The "Originating event" field of filtered contacts in your segment is blank, and you might added some contacts to your event manually,
while field which is used in dynamic expression is required to has a valid value.
Actually from my test, email to Kiyomoto Tomoki is blocked by same reason as your issue mentioned due to this.
Conclusion:
1. If you would like to send email to contacts who submit event registration form, then your segment should be below:
and dynamic expression still keeps same as the above.
2. If you would like to send email to contacts who were added by yourself manually:
At beginning you need create a single text field to event registration entity and create a workflow to sync their parent event formatted name to the field because:
1. dynamic expression can only display lookup field id value.
2. dynamic expression is limitted to get contact's directly related records.
Then you could retrieve the contact's registrated event name by a for each snippet by adding a custom code element to marketiing email:
{{#each contact.msevtmgt_eventregistration_contact_msevtmgt_contactid}}
{{this.new_formateventname}}
{{/each}}
(If segment is what you posted)
Please read docs below:
Understand relationship definition in segment drop down list:
https://docs.microsoft.com/en-us/dynamics365/marketing/segments-profile#move-between-entities-with-relationships
Understand relationship definition in assis-edit:
https://docs.microsoft.com/en-us/dynamics365/marketing/dynamic-email-content#how-assist-edit-presents-database-relationships
How to use foreach in marketing email(it would be easy to use after understanding relationship definition for both segment and assis-edit):
https://docs.microsoft.com/en-us/dynamics365/marketing/dynamic-email-content#for-each-loops
Regards,
Clofly
