Dynamics 365 brings the ERP offerings of Microsoft to a new level as we take the full step to Software-as-a-Service offering (SaaS). This requires that solutions are designed, developed, tested, maintained and marketed in new ways – at least for the traditional Dynamics partner.
In SaaS, the source code has to stay the same and every additional functionality needs to be examined to make sure that the design is in line with the strategy of the solution and that it is kept secure. For Dynamics 365, one of the key elements when designing a solution is to keep it in line with Microsoft’s philosophy for the service i.e., it has to be simple and intuitive to use.
In order to build Dynamics 365, Microsoft has scaled down the traditional functionality in Dynamics by adding a meta-layer. This, in effect, keeps full functionality in place but limits the user to work with the functionality that offered by the Business and Enterprise editions. The reason for this is that Microsoft wants a fast adoption rate for the new product using e-learning and user guides within the system. Essentially, users should be able to, more or less, figure out how to use the service themselves.
This situation means that when designing an App for Dynamics 365, the functionality and processes that are available to users need to be considered first with an eye to possible future new functionality. This to ensure that any solution offered is intuitive to the user and is embedded in the CDM. However, when building the App for Dynamics 365, the solution is built within the full application and then extended from the standard code.