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
Since the Unified Interface is the recommended way for Dynamics 365 and Unified Interface need Custom Control Framework to add some customization, Do we have any compatibility chart or known guidelines on what does custom control framework supports?
Does Custom Control Framework is back word compatible with classic UI and to what extent?
something like below
Dynamics CRM 8.2
Dynamics CRM 9.0 ON-Premise
Dynamics CRM 9.0 Cloud
Classic UI - Multi Section
Classic UI - Web Resource
Classic UI - Iframe
Unified Interface UI - Multi Selection
Unified Interface UI - Web Resource
Unified Interface UI - Web Resource - CCF
Classic UI is nearing its end-of-life. "Customers must transition to Unified Interface before October 1, 2020."
So I would not expect the PowerApps Component Framework - PCF (earlier CCF - Custom Control Framework) to be compatible with classic UI. Its just for UCI. Also the same PCF control should work for Canvas apps in future (as per Product Roadmap).
Yes, some control like Flip switch, Editable Grid worked in both Classic & UCI, but those are OOB controls from initial days.
Thanks for the reply. Yes that's true, we can probably guess from the Roadmap. Strategic decisions are some time puzzly.
Type of Customization that can be compatible on everywhere (8.2/9.0/ClassicUI/Unified Interface/Legacy Rendering all) seems to be Web Resource with supported API endpoint's then, is that accurate? Web Resource on Unified INterface still works, correct? Any thoughts on that?
Yes, Web resource is the only compatible step across versions/UI :)
Certain Methods for Xrm.Page in web resources still works on both classic UI and Unified Interface UI as well.
ExecutionContext.getFormContext will not work in the HTML Web resource still.
important changes coming
Business Applications communities