Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
This part of our blog series will cover the most common correlation method used for automatic promotion for user mailboxes: In-Reply-To correlation.
From our previous entry, we have an email sent from Dynamics that has the following Message-ID:
Exchange handles replies and forwards a bit differently than sending brand new emails. Let's reply to this email from my inbox and see what the reply's message headers look like:
From: Cody Dinwiddie <email@example.com>To: Cody Dinwiddie <codin@OBFUSCATED.onmicrosoft.com>Subject: Re: Test EmailThread-Topic: Test EmailThread-Index: AQscuKgXz0bUld+ni9oW2WvWgJcWopbHxZqCDate: Tue, 1 Sep 2020 20:07:11 +0000Message-ID:<CH2PR21MB1463D383FECE14183B853DF7AE2E0@CH2PR21MB1463.namprd21.prod.outlook.com>References:<142408F2977449AE9A3EB234870D156A1D6809716A2B@CODIN.OBFUSCATED.ONMICROSOFT.COM>In-Reply-To:<142408F2977449AE9A3EB234870D156A1D6809716A2B@CODIN.OBFUSCATED.ONMICROSOFT.COM>Accept-Language: en-US
This message has some additional fields than what we saw on a brand new email: "References" and "In-Reply-To". Notice how the MessageID is unique, but the In-Reply-To value is identical to the message id of our original email (the one we replied to). When Server-Side Sync reaches out to Exchange and pulls all of the emails since they last spoke, the following happens (simplified overview):
Since we have a match, We will create the record in Dynamics:
Remember when I said that Exchange also applies "In-Reply-To" values to forwards as well? Let's take a look at the headers of a forward of the same forwarded mail:
From: Cody Dinwiddie <firstname.lastname@example.org>To: John Doe <jodoe@OBFUSCATED.onmicrosoft.com>Subject: Fw: Test EmailThread-Topic: Test EmailThread-Index: AQscuKgXz0bUld+ni9oW2WvWgJcWopbHyrhBDate: Tue, 1 Sep 2020 20:25:32 +0000Message-ID:<CH2PR21MB1463E1A0575C6B54502AADC3AE2E0@CH2PR21MB1463.namprd21.prod.outlook.com>References:<142408F2977449AE9A3EB234870D156A1D6809716A2B@CODIN.OBFUSCATED.ONMICROSOFT.COM>In-Reply-To:<142408F2977449AE9A3EB234870D156A1D6809716A2B@CODIN.OBFUSCATED.ONMICROSOFT.COM>Accept-Language: en-US
All users are setup to promote in-reply-to matches by default. In the above scenario, if John Doe is a Dynamics user setup to have incoming email evaluated through Server-Side Sync, John will see the above email and automatically promote it to Dynamics, thinking it is a direct reply. This scenario is not very common, but can still occur, so it's really important to understand the properties we evaluate for automatic promotion into Dynamics.
Due to this behavior, I worked with my colleague Ben Merrill to develop a plug-in that evaluates inrpelyto correlated mail and prevents forwards from promoting to the instance if the sender of the original forwarded mail is not a recipient on the forward. You can find this code here:
Be aware that this sample code is provided for the purpose of illustration only and is not intended to be used in a production environment. Please review the coded for details on its use and trigger mechanisms.
In our next series, we will dive into Tracking Token and Smart Matching correlation. See you soon!
Part 1, Part 2, Part 3
Business Applications communities