Dynamics AX

Dynamics AX

-

English

Description

Axapta is Microsoft’s flagship ERP system and the most exciting ERP product currently on the scene. If Axapta hasn’t come to a computer near you yet, it will soon. ?Note This book is based on Axapta version 3.0. Shortly before this book went to press, Microsoft announced that Axapta was to be rebranded as Dynamics AX.Axapta and Dynamics AX are one and the same product, and in this book we consistently use the term Axapta because that is the term that will be commonly used in the field for the near future. We’d like to start by offering the most valuable piece of advice we have for anyone wo- ing with Axapta (and with any complex system, for that matter): Keep it simple. Implement it in clearly defined and documented increments. For business consultants, architects, and developers we would add this: stick to standards whenever possible, develop simple so- tions, and keep the code simple and well-commented.

Subjects

Informations

Published by
Published 05 November 2006
Reads 32
EAN13 9781430200789
License: All rights reserved
Language English

Legal information: rental price per page €. This information is given for information only in accordance with current legislation.

Report a problem
Axapta is Microsoft’s flagship ERP system and the most exciting ERP product currently on the scene. If Axapta hasn’t come to a computer near you yet, it will soon. ?Note This book is based on Axapta version 3.0. Shortly before this book went to press, Microsoft announced that Axapta was to be rebranded as Dynamics AX.Axapta and Dynamics AX are one and the same product, and in this book we consistently use the term Axapta because that is the term that will be commonly used in the field for the near future. We’d like to start by offering the most valuable piece of advice we have for anyone wo- ing with Axapta (and with any complex system, for that matter): Keep it simple. Implement it in clearly defined and documented increments. For business consultants, architects, and developers we would add this: stick to standards whenever possible, develop simple so- tions, and keep the code simple and well-commented.