Book Image

Implementing Microsoft Dynamics 365 for Finance and Operations

By : Rahul Mohta, Yogesh Kasat, JJ Yadav
Book Image

Implementing Microsoft Dynamics 365 for Finance and Operations

By: Rahul Mohta, Yogesh Kasat, JJ Yadav

Overview of this book

Microsoft Dynamics 365 for Finance and Operations, Enterprise edition, is a modern, cloud-first, mobile-first, ERP solution suitable for medium and large enterprise customers. This book will guide you through the entire life cycle of a implementation, helping you avoid common pitfalls while increasing your efficiency and effectiveness at every stage of the project. Starting with the foundations, the book introduces the Microsoft Dynamics 365 offerings, plans, and products. You will be taken through the various methodologies, architectures, and deployments so you can select, implement, and maintain Microsoft Dynamics 365 for Finance and Operations, Enterprise edition. You will delve in-depth into the various phases of implementation: project management, analysis, configuration, data migration, design, development, using Power BI, machine learning, Cortana analytics for intelligence, testing, training, and finally deployment, support cycles, and upgrading. This book focuses on providing you with information about the product and the various concepts and tools, along with real-life examples from the field and guidance that will empower you to execute and implement Dynamics 365 for Finance and Operations, Enterprise edition.
Table of Contents (23 chapters)
Foreword
Title Page
Credits
Disclaimer
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Importance of testing


Testing is the process of validating the system processes to meet the business requirements. It includes testing the custom as well as the standard features, along with the migrated data, integrations, reports, and security aspects of the solution. It is an area that is most often underestimated and, as a result, hampers the success of your project.

A very common misconception is that testing starts after the development phase is over. The primary goal of testing is to provide feedback on the product as soon as possible. Identifying any issues in the requirements phase prevents them from becoming a part of the design. Similarly, identifying any issues in the design phase prevents them from being coded. The cost of fixing a defect depends on the phase where it has been detected; the cost of fixing a defect in the early phases of SDLC (Software Development Life Cycle) is much lower in the later phases. The farther you go with the backlog of testing/validation; the more...