The message should have gotten through load and clear by now, customisation of Dynamics 365 for Operations (AX7) should, wherever possible, be done using Extensions. Your development team should have seen this being hammered home by Microsoft and the D365 community over the past months and especially since Microsoft told us that the Application Suite will be sealed by spring 2018. So how do you stop your development team from falling back on old habits by using their tried and test over layering techniques?
Dynamics 365 for Operations (AX7) Electronic Reports are used for statutory or country specific document purposes. The Microsoft repository contains a lot of document types out of box, but sometimes we need to create custom document. Let’s look at the scenario when we need to create electronic report for Sales Packing Slip.
There are two ways of running an Electronic Report:
- From the Electronic Reporting module, by selecting a configuration and running it.
- From a menu item, by linking a service to a proper Electronic Reporting configuration.
Both of these methods need a properly configured model and configuration and in this post we’ll discuss how to do this. Continue reading
When Microsoft started releasing hotfixes for the Dynamics AX 2012 R3 release they made our lives a little harder. If you had just one or two hotfixes load it wasn’t too bad but as eventually you find yourself loading a hotfix that has hundreds of dependant hotfixes and suddenly your model store has a list of models a mile long in it. So, when you’re promoting code from your Development system through to Test and Production you need to be sure that you have all the right hotfixes loaded and with a long list of models in each model store, you can easily make a mistake and miss something.