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.

Preface

What this book covers

Who this book is for

Starting a New Project

Starting a New Project

Technical requirements

Creating the Azure DevOps project

Connecting Visual Studio to Azure DevOps

Creating a new package and model

Configuring project and build options

Creating a Label file

Free Chapter

Data Structures

Data Structures

Technical requirements

Creating enumerated types

Creating extended data types

Creating setup tables

Creating a parameter table

Creating main data tables

Creating order header tables

Creating order line tables

Creating the User Interface

Creating the User Interface

Technical requirements

Creating the menu structure

Creating a parameter form

Creating menu items

Creating setup forms

Creating details master (main table) forms

Creating a details transaction (order entry) form

Creating form parts

Creating tiles with counters for the workspace

Creating a workspace

Adding a filter to a workspace

Working with Form Logic and Frameworks

Working with Form Logic and Frameworks

Technical requirement

Creating a table handler class

Creating a form handler class

Hooking up a number sequence

Creating a create dialog for details transaction forms

Updating form controls at runtime

Application Extensibility

Application Extensibility

Technical requirement

Adding fields to a standard table

Writing data-event handlers

Using a Chain of Command to initialize data

How to customize a document layout without an over-layer

Modifying a standard form

Using Chain of Command with a form

Replacing a standard lookup with our own

Adding a form display method to a standard form

Writing for Extensibility

Writing for Extensibility

Technical requirements

Writing and using delegates

Using the attribute framework to construct classes

Creating a purchase order programmatically

Creating a facade

Defining business actions in data

Creating a SysOperation process

Adding an interface to the SysOperation framework

Using SysOperationSandbox

Advanced Data Handling

Advanced Data Handling

Technical requirements

Implementing table inheritance

Using menu items to create records for tables that use inheritance

Using date-time effectiveness

Creating a view with a query and computed columns

Business Events

Business Events

Technical requirements

Creating a new business event

Creating an Azure Service Bus queue

Configuring the business event to use a Service Bus queue

Creating a Microsoft Flow to receive the Service Bus queue message

Receiving messages in SCM from the Service Bus

Security

Technical requirements

Creating privileges

Creating duties

Creating security roles

Creating policies

Data Management, OData, and Office

Data Management, OData, and Office

Technical requirement

Creating a data entity with an Edit in Excel experience

Extending standard data entities

Importing data through the Data Import/Export Framework

Reading, writing, and updating data through OData

Consuming and Exposing Services

Consuming and Exposing Services

Technical requirement

Creating a service

Consuming a SOAP service in an external application

Consuming a JSON service in an external application

Consuming an external service within F&O

Unit Testing

Technical requirements

Creating a unit test project

Creating a unit test case for code

Creating an Acceptance test library entity class

Creating an Acceptance test library specification class

Creating an Acceptance test library data class

Creating an Acceptance test library data class structure

Creating an Acceptance test library class that ensures a process can be done

Automated Build Management

Automated Build Management

Technical requirements

Creating a Team Services Build Agent Pool

Setting up a build server

Managing build operations

Releasing a build to User Acceptance Testing

Workflow Development

Workflow Development

Technical requirements

Creating a workflow type

Creating a workflow approval

Creating a manual workflow task

Hooking up a workflow to the user interface

Creating a sample workflow design

State Machines

Technical requirements

Creating a state machine

Creating a state machine handler class

Using menu items to control a state machine

Hooking up the state machine to a workflow

Other Books You May Enjoy

Other Books You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Implementing table inheritance

Table inheritance can be implemented so that we have a base table with common attributes, as well as specializations that extend that table and add their own attributes and methods. This is similar to classes, but only in concept—although the base table can have many child tables, only one physical table is created in the SQL Server. The physical table in the SQL Server contains all of the fields from the base table and its child tables.

A good candidate for this is the vehicle table, where we could have a base vehicle table and a child table for each type, such as Bike, Car, and Truck. This is suitable as long as we are sure these can be considered physical data structures, and not a categorization. For example, we can change a product from inventory to non-inventoried by changing the inventory model group, but we cannot change a vehicle...