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
About the Author
About the Author
About the Reviewers
Testing and Training

Approaching performance issues

Performance issues can be due to many factors, and to identify the root cause, you may need to involve multiple groups within the organization. This makes it challenging and, sometimes, even political. Also, performance issues are complex and hard to reproduce. Therefore, it's important to understand the issue clearly, set priorities, and get the appropriate people involved for the analysis.

Understanding the issue

The very first step is understanding the issue. "We are having performance issues!" is a very broad statement. You need to identify all the symptoms, and these symptoms may help you define the course of action. It's important to ask the right questions, such as:

  • How many users are affected and in what areas of the business?

  • Is this a general performance issue or related to specific processes?

  • Is there a pattern for the issue like particular users and/or times of the day?

  • Can it be recreated in a test environment? If not, can it consistently be recreated...