Bring your code 2 life

In version 1710 (9.0.2.2279) of Dynamics 365 Online we get this dialog to create a new app… As you can see it contains the Client options Web and Unified Interface. After an automatic minor update to the newer version 1710 (9.1.0.33) online you only have this dialog available. This version creates a unified interface app by default and you cannot create apps with a web interface anymore. Microsoft is transitioning from the classic web interface to the relatively new unified interface. Is this the version where we cannot create new web interface based apps anymore? Either this is a bug or we face the next wave mentioned in Steve Mordue’s article: https://stevemordue.com/the-transition-to-unified-interface/

Field Service added some new forms to entities like opportunity, quote, order, etc. as well as a JavaScript library running on these forms. Now if you had copied a form based on a FS form then with an earlier version of Field Service you would have received this error everytime you try to save or load a record. TypeError: Cannot read property 'Metadata' of undefined at Object. GetOrderType (https://crm365.testqa.company.dev/CustomerDev/%7B636718359380000112%7D/WebResources/msdyn_/SalesDocument/SalesDocumentFormLoader.Library.js:1:5679) at Object.FormApplies (https://crm365.testqa.company.dev/CustomerDev/%7B636718359380000112%7D/WebResources/msdyn_/SalesDocument/SalesDocumentFormLoader.Library.js:1:4312) at Object.OnLoad (https://crm365.testqa.company.dev/CustomerDev/%7B636718359380000112%7D/WebResources/msdyn_/SalesDocument/SalesDocumentFormLoader.Library.js:1:909) at https://crm365.testqa.company.dev/CustomerDev/%7B636718359380000112%7D/WebResources/

On a customer tenant we had the issue on some orgs that with SLA feature enabled on the entity work order the transferred solution created on the target system fields with lower case schema names: DEV-System with proper schema names: Exported as managed solution and then imported to a Dynamics 8.2.2.x Online system: => now with wrong lower case schema names Microsoft confirmed in our support case that this is a bug and it was fixed in this version: Microsoft Dynamics 365 Version 1612 (8.2.2.2518) (DB 8.2.2.2464) online