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
we have a 2015 CRM On-Premise that sends out emails just fine.
We have a 2016 version of the same organization that we created.
When I create an email activity, fill it out and click Send, first I get the box telling me "your changes have not been saved" (??)
When I click Cancel, I get "Access is denied", and when i download the log file it complains that you "Cannot update parties unless email is in draft status."
(Sometimes it complains about the subject/description...)
If I click OK, it sends out the email....
Any ideas why this is happening?
I have tried it with the infamous "use legacy form rendering" set to yes and no - same behaviour.
Any assistance appreciated.
Check this link: community.dynamics.com/.../83984.aspx
This link offers some solutions to the Outlook plugin not sending emails that are in Pending Send status.
Basically it could either be a configuration in Outlook itself, or a security permission for the user running the workflow.
This may help you use the Create Record Step vs the waiting step.
I Hope this helps.
Hope this helps.
Business Applications communities