Share
Report
30A customer is implementing a new website which will enable multiple webforms for customers to use when wanting to get in touch with them.
The requirements were made based on their current e-mail handling system and we were involved quit late in the process since they decided not that long ago to replace their current e-mail handling system.
The streight forward way of handling this would be to implement an API call and thus create an activity / case after submitting the webform.
But given their current e-mail handling system, the choice was made to send an e-mail from a no-reply@xxx email address to a mailbox, with the actual customer in CC - the email will not be send to the customer!
Because of the given timelines - the website will have to go live with that implementation instead of an API call.
So I'm looking for a way to handle e-mails coming in on a on-premise exchange server - linked to a cloud D365 CE solution. Where I want to use the e-mail address in CC to identify the customer and create a case for it.
Problem 1: the CC is not a field of the e-mail entity - but a writable attribute - how do I access that information?
Problem 2: any ideas on the easiest way forward :-)? I think I can't solve this with build-in e-mail routing & record creation functionality. But I should rather do it in flow? How do I implement an easy logic in flow to 'get record' (D365) on entity contacts - where the e-mail address is the e-mail address in the CC of the e-mail?
Hope someone has an enlighting idea :-)
Cindy
All responses (
Answers (
