Book Image

Implementing Microsoft Dynamics 365 for Finance and Operations Apps - Second Edition

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

Implementing Microsoft Dynamics 365 for Finance and Operations Apps - Second Edition

By: JJ Yadav, Sandeep Shukla, Rahul Mohta, Yogesh Kasat

Overview of this book

Microsoft Dynamics 365 for Finance and Operations is a modern cloud ERP platform that adopts a mobile-first approach suitable for medium-to-large enterprises. This book covers the entire implementation process of Dynamics 365 Finance and Operation Apps, including post-implementation and business transformation. The updated second edition starts with an introduction to Microsoft Dynamics 365, describing different apps and tools under it. You will learn about different implementation methodologies such as Waterfall and Agile, for your projects. We will cover various application components and architectures of Dynamics such as requirements processing, development, reports and analytics, and integration. With the help of tips, techniques, and best practices, you’ll explore strategies for managing configurations and data migrations. As you read further, you’ll discover development tools and processes in Dynamics for building customized solutions in Dynamics. The book will also demonstrate analytics and financial reporting options such as Power BI and Cortana Intelligence. Finally, you’ll learn the importance of testing and explore various automated testing strategies. By the end of this book, you will have gained the necessary knowledge to implement Microsoft business solutions with Dynamics 365 for Finance and Operations Apps.
Table of Contents (15 chapters)

The importance of testing

Testing is the process of validating the system and processes in order to meet 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 the Software Development...