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)

Working with Form Logic and Frameworks

In this chapter, we will get straight into writing code. The recipes chosen for this chapter are common tasks that will be used on many development projects.

As we progress through this chapter, references to code placement will be made. Code placement is critical to a maintainable and extendable solution. We will see that code can be written on the form, in a class, or in a table. The rule of thumb here is that we must place code as low in the stack as possible. If we write code on a form, that code is only available to that form and cannot be reused. This is fine when we are hiding a button, but data (validation and other data-specific code) logic usually belongs to a table. As the code on the form or table gets more complicated, the code should be moved to a class.

The SalesTable form and table is an example. In this case, table events...