Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
The new Common Data Service for Apps promises to deliver the Xrm platform that we've been after for - well since forever! Today it was announced that it's no longer in Preview and has made it to General Availability (GA)!
Of course, with any GA announcement there is also a raft of licensing questions – the most important one for me was around how we can license the CDS for Application and build Model-Driven Apps without licensing for the Dynamics 365 1st Party Apps such as Sales & Servicing.
With the licensing documentation released today, Plan 2 appears to be that XRM type licensing, allowing building of Model Driven Apps (Dynamics Apps rather than Canvas Apps) with features such as real-time workflows and plugins.
The official license page shows a full breakdown of the license features, but below I've extracted the most important aspects with respect to building Model Driven Apps that we know as Dynamics 365 App Modules.
You can see that Plan 2 allows us to build Dynamics Apps without actually having a D365 license – with the exception of this new term 'restricted entities'. Conveniently, there is a list of which entities these are and the associated Dynamics 365 license required. The main take away is that you need a Customer Service license for full access to entities such as case/kbarticle/SLA and Project Service/Field Service license for the unified scheduling entities – with Plan 2 these restricted entities are read-only. This makes sense, as these entities are required by special functionality that is specific to those 1st party Apps that can only be accessed as part of a Dynamics 365 license.
It's worth noting that you can build Model Driven Apps with Plan 1 – but you can only use Async Workflows and Business Rules inside the CDS.
Why not learn more here:
Watch my video about how the Common Data Service for Apps is the new XRM Platform:
Business Applications communities