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
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 am a bit stuck here. I'm unable to qualify leads when the Lead Type is "Work based". It fails with the following error message:
"Attribute 'msdyn_contractorganizationalunitid' cannot be NULL".
I tried the solution provided by Dominic Carvalho in this thread https://cCannot qualify Lead to Opportunity on a Sandbox D365 online instance.
I even deactivated the "Project Service - Contracting Unit is Required" business rule on the Opportunity record. Still fails.
This started I think when I changed the Project service > Settings > Parameters > Default Organizational Unit
I assume I'm missing a setting or configuration somewhere, but I haven't found the minimum required settings for this to work.
Your help would be much appreciated.
Please make sure the Contracting Unit field is populated when the user creates in opportunities in the Application
Business Applications communities