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 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 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
I just need a information about Async service and Workflow in CRM 4.0. In our client system there are more than 10000 workflows are in waiting state (from March 1, 2016 to till date).
When user tries to run a workflow (which will create folder in SharePoint), it's not creating. Previously it was creating but not now. Whether the waiting workflow in the Async will be issue or Async service will be in heavy load to handle new workflow?
Else what will be the issue? Is it good practice to keep 10000 count of workflow in waiting state? (Day by day it will increase). Suggest me to handle this situation.
Business Applications communities