Upgrading to D365 - Development Implications

Microsoft Dynamics 365 is a SaaS application that lives in the cloud. You no longer have direct access to the database.

In this video, you'll learn how to work within the app framework and use APIs to connect to the data, as well as how to leverage middleware. We'll address the integrations lifecycle, including analysis, building and deployments, testing, and overall strategy considerations.

D365UpgradeSeries_6_DevelopmentImplications

Development Implications Takeaways

The biggest architectural change to Dynamics 365 from Dynamics AX 2009 or 2012 is that the production instance is now a SaaS application (software as a service). D365 is a cloud application. You can take advantage of cloud-based version control and environment management, Dev Ops strategies, and more easily integrated applications.
With Microsoft responsible for the service level agreement, continuous updates are a part of their support strategy. Think of it as an evergreen application with every customer on the latest release. This approach ensures that all users are on a reliable and robust version of the application.
This move to the cloud means that the development shifts from an overlaying model to extension-based development experience. All development is performed through Visual Studio which provides better IntelliSense and a more robust developer experience. The compiler has also been re-written resulting in faster build times, more up-to-date cross-references, and a better experience from development to deployment.
Testing is critical with continuous updates. With more frequent updates, consider automating more of your tests and using automated testing libraries. In addition to testing new functionality, you’ll also perform regular regression testing. Minimizing customizations simplifies testing.