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

The functional design document


In the previous section, you learned how to provide solutions for the identified feature gaps by using ISV solutions or utilizing some of the common features and tools available. The next step is to start the design process for the requirement gaps that still do not have a home in the solution. The functional design documentation (FDD) describes the features of the desired customizations. The document can include things such as flowcharts, screenshots, wire frames, and so on. At a minimum, an FDD will contain an organized list of requirements that can be used for development, testing, and client sign off. Before going further with the details of why functional design is important, what it should cover, and best practices, let's first learn about the process of the fit-gap review session, which is critical before moving forward with writing an FDD.

The fit-gap review session

The fit-gap document is the primary input document to write the FDD. It is very important...