Book Image

Extending Microsoft Dynamics 365 Finance and Supply Chain Management Cookbook - Second Edition

By : Simon Buxton
Book Image

Extending Microsoft Dynamics 365 Finance and Supply Chain Management Cookbook - Second Edition

By: Simon Buxton

Overview of this book

Dynamics 365 Finance and Supply Chain Management is Microsoft’s ERP solution, which can be implemented as a cloud or on-premise solution to facilitate better decision-making with the help of contemporary, scalable ERP system tools. This book is updated with the latest features of Dynamics 365 Finance and Supply Chain Management including Chain of Command (CoC), Acceptance Test Libraries (ATL), and Business Events. The book not only features more than 100 tutorials that allow you to create and extend business solutions, but also addresses specific problems and offers solutions with insights into how they work. This cookbook starts by helping you set up a Azure DevOps project and taking you through the different data types and structures used to create tables. You will then gain an understanding of user interfaces, write extensible code, manage data entities, and even model Dynamics 365 ERP for security. As you advance, you’ll learn how to work with various in-built Dynamics frameworks such as SysOperation, SysTest, and Business Events. Finally, you’ll get to grips with automated build management and workflows for better application state management. By the end of this book, you’ll have become proficient in packaging and deploying end-to-end scalable solutions with Microsoft Dynamics 365 Finance and Supply Chain Management.
Table of Contents (17 chapters)

Releasing a build to User Acceptance Testing

At the end of the build process, a deployable package file was uploaded to the build. This file can then be applied to your user acceptance test or sandbox server.

We can apply the package manually on the test server but, for LCS-deployed User Acceptance Testing (UAT) environments, this is always done via LCS. Any release to production must be deployed to a sandbox server first and marked as a release candidate.

A simplified process for the release to UAT would involve the following steps:

  1. The development team writes code and completes the tasks that are required for the next build (for example, those that are assigned to the current sprint).
  2. The developers will also write unit tests and perform their own unit tests.
  3. Initial testing will be done by taking a package from the Dev branch pipeline and deploying it to a OneBox. This is...