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)

Workflow Development

Workflows in Microsoft Dynamics 365 Finance and Supply Chain Management have two main types of elements – approvals and tasks – that act on a document. This is the center of the workflow and is where tasks are triggered based on what the user decides. By document, we mean a record with a form that maintains it. For example, a New customer creation workflow would be based on the customer table using the customer details form as the document.

The workflow designer can then use conditions based on fields and display methods on tables in order to decide what happens. This solves many requirements where a great deal of flexibility in the configuration is required, but can also be misunderstood and used inappropriately. The submission of a workflow is usually started with the user pressing the Submit button on the form; it's which is then processed...