A 3-Day evaluation of how to refactor your ISV solution to use Dynamics 365 extensions.
In Dynamics 365 for Operations, code in overlays must be refactored into extensions within its own package to comply with Microsoft best practices. Unlike overlayering, extensions reduce the cost of upgrading to a new version, as this approach eliminates costly code and metadata conflicts.
Use SAGlobal's FREE 3-day assessment to find out what development effort is required to refactor your ISV application's code that was done using overlayering to extensions.
Until recently, overlaying code was the only way partners and customers were able to offer customizations for industry requirements due to Dynamics 365 for Operations 3-tier infrastructure. By the sheer nature of the software, some invasive overwriting was bound to occur.
With Microsoft Dynamics 365 for Finance and Operations, developers are required to create extensions that interact with, but don’t alter, Dynamics 365 for Operations source code. Microsoft introduced this feature to make it easier for customers to incorporate industry-specific solutions into their Dynamics 365 for Operations instances.
Code extensions are incredibly useful when you consider that, like most cloud-based products, Dynamics 365 Enterprise Edition receives regular and frequent updates to ensure users are always getting the latest and greatest product. So the great benefit is that code extensions don’t break after you run an update. The latest version of Dynamics 365 for Operations simply searches for the existing extension and picks up right where it left off.
A report on the estimated effort required to convert your ISV solution to a fully extended application within Microsoft Dynamics 365.