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 2 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 had a workflow in our existing CRM environment that does validation on the lead entity as the stage is about to change. Basically it validates that before you move to 'stage 3', a field must be in the range of accepted values in 'stage 2'. A part of this logic was as follows:
When we upgraded our non-production environments, this workflow stopped working as expected. I know that with the upgrade to 365, the business process flow structure and relationships had changed but what I found here was that the values being used to compare were the values before the change occurred and not after, even though the workflow setup hadnt changed:
Quick fix in our setup was instead of checking if the current stage is 'stage 3', we changed the logic to see if it was 'stage 2' and looking to go to 'stage 3'
Hope that helps!
Business Applications communities