In most books that outline the ERP implementation best practices, customization is a bad word. However, in reality, one can't avoid it completely in the project. Hence, the ease of use in the development platform and the variety of tools available play a key role in the selection of an ERP system. One of the key reasons why Microsoft Dynamics AX is selected over the other ERP systems is the availability of the broad variety of technology toolsets for building additional solutions. The best practices need to be followed to ensure that the customizations are kept to a minimum, they avoid altering the core foundation of the product, and enough thought is put into making them 'temporary' and upgrade-friendly. I will explain the concept of temporary later in the chapter.
Dynamics AX provides a layered-development approach, where the partners, ISV Solutions, and the customers each have a layer where they can make the customizations without disrupting each other...