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
Scenario: Contact emails in our build of CRM only go to to the nominated "preferred" email address. Contact wants an email to go to an email address that is on their contact record but is not the preferred email address. The email address is typed in to to "To:" field and is recognised as an email linked to that contact by CRM which then displays the contact name instead and sends the email to the preferred email address instead.
Query: How does the CRM user send an email to a non-preferred email address without having to change the preferred email address on an ad hoc basis for this one email and then undo this change immediately afterwards please?
CRM 2013 on premises (without Outlook Connector).
Dynamics can only send the primary email address by default - the easiest solution is to create another contact since a contact record is purely about how to contact the person rather than a unique person record. You can link the two records together using connections. Sounds counter productive to create two contacts I know!
Hope this helps
I also used to create additional custom entity (linked to the contact entity through 1:N, for example) just for "emailing". Put a lookup to a contact entity from that custom entity, then, for each of the contact emails, create a new record of that custom entity type. Might also add a workflow/plugin to automatically add all those "linked emails" (custom entities) to the email "to" field whenever sending an email to a contact.
Hi Richard Kirkham,
you could use this "fast and dirty" solution:
1) create a workflows to send email
2) check inside it if there is a secondary (and even other) email address of contact is not empty
3) if true, check if exists a contact with the same name+cc (example: "John Doe (cc)" and principal email address filled with secondary email address and reactivate it (see next point to understand it); if not create it
4) add this contact to cc field
5) send mail
6) deactivate contact
This work like a charm, the unique blame is you will have an inactive duplicated contact.
Please let me know if you solve.
If you found the answer helpful, please mark as Verified
Join my network on LinkedIn Follow me on Twitter
Thank You & Best Regards
Microsoft Dynamics CRM Consultant, Bologna+Milano, ITALY
Thanks Scott, Alex and Francesco for taking the time and trouble to reply. It is appreciated. I do understand the new contact route.
The email functionality in the CRM 2013 web client could really benefit from development by Microsoft but reading other threads on it and Microsoft's replies it has become apparent that it has no intention to do so.
Given the importance my organisation gives to data cleansing and deduplication of records I think we will have to stick to toggling the preferred email settings in such situations.
Dear Colleagues! Is there a way to prevent D365 from populating the To: field with the email address and let a user select it? Thanks, Nikita
Hi Nikita. We haven't migrated to D365 yet but will do in the summer. I'll check again then and update (and if you hear something positive do please let me know). Thanks.
Business Applications communities