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
I just patched our On Premise Dynamics CRM 2015 to 220.127.116.11 and noticed some odd behavior with background workflows. Any background workflow that assigns a record to a team or user no longer works. It comes back as succeeded, but the record has the same owner. If I switch it to real time, it works but I start getting errors after awhile about "all entities must be found". I can also click the "Assign" button and manually assign records. Looked through the application logs and couldn't find anything. Any idea what is going on? Did the background workflow process change so I can no longer reassign records as they come into the system?
Business Applications communities