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)

Automated Build Management

In this chapter, we will cover the steps that are required to set up and use a build server. We touched upon some of the benefits of a build server in Chapter 12, Unit Testing, where unit tests can be executed to help reduce the risk of regression.

We shall cover two scenarios: a cloud-hosted customer implementation project deployed via LCS, and an on-premise build server, which is equivalent to an Azure server hosted under your own subscription.

If the implementation is hosted in Azure and is deployed through an LCS customer implementation project, all we need to do is set up Build Agent Pools and then supply parameters to the setup form in LCS. The process of deploying a build machine is well documented and we won't duplicate this here, especially given the pace at which updates to LCS are being made. Even if we don't set up a build server...