Book Image

Microsoft Dynamics AX Implementation Guide

By : Yogesh Kasat, JJ Yadav
Book Image

Microsoft Dynamics AX Implementation Guide

By: Yogesh Kasat, JJ Yadav

Overview of this book

Microsoft Dynamics AX is Enterprise Resource Planning (ERP) software that supports multi-site operations across various countries, providing international processing within the company. It is an ERP solution with a lot of features and functionality, and it provides support across the fields of financial, distribution, supply chain, project, customer relationship, HR, and field service management. This book is all about simplifying the overall implementation process of Dynamics AX. The purpose of this book is to help IT managers and solution architects implement Dynamics AX to increase the success rate of Dynamics AX projects. This all-in-one guide will take you through an entire journey of a Dynamics AX implementation, ensuring you avoid commonly-made mistakes during implementation. You’ll begin with the installation of Dynamics AX and the basic requirements. Then, you’ll move onto data migration, reporting, functional and technical design, configuration, and performance tuning. By the end of the book, you will know how to plan and execute Dynamics AX right, on your first attempt, using insider industry knowledge and best practices.
Table of Contents (23 chapters)
Microsoft Dynamics AX Implementation Guide
Credits
About the Author
Acknowledgments
About the Author
About the Reviewers
www.PacktPub.com
Preface
11
Testing and Training
Index

Coding best practices


In this section, we will learn some best practices to be followed during development in Dynamics AX.

Best practice check

Run your code through the X++ best practices process, evaluate all the best practices errors and warnings, and take the appropriate action.

Naming variables and objects

Begin the variable and method names with lowercase letters like custTable, validateFields, and so on. Begin the names of the AOT elements with capital letters such as CustTable, SalesFormLetters, and so on.

Prefix the parameters names with an underscore (Args _args). Use meaningful and self-explanatory variable names. For example: SalesTable salesTable and not SalesTable table1

Commenting the code

Code comments enhance the readability of the code and are very useful for those involved in modifying or maintaining the code. Comments should be used to describe the intent, algorithmic overview, and the logical flow.

Add XML documentation for class, class methods, and table methods. You can generate...