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

By : Simon Buxton

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

Sections

Get in touch

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

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

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

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

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

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

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

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

Technical requirement

Introduction

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

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

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

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

Leave a review - let other readers know what you think

Customer Reviews

5 star

4 star

3 star

2 star

1 star

Data Structures

In this chapter, we will cover the tasks required to write the data dictionary elements commonly used within Supply Chain Management (SCM) development.

Data structures in SCM are not just tables and views—they also include the ability to define a data dictionary. This is now called the data model in SCM. The data model hasn't changed much in structure since AX 2012, but is much more refined, with many more features to aid development and minimize the footprint when extending standard tables and types.

This chapter does not cover creating extensions of standard types, but it does cover how to create types that allow your structures to be extensible. Extensibility is covered in Chapter 5, Application Extensibility.

Most development in SCM is based on patterns, even if we are not aware of it. This classically means code patterns, but SCM unifies the code, data model, and user interface design. So we have patterns to follow when creating the data model. For example, the vendor and customer lists are very similar and are called main tables. Purchase orders and sales orders are also very similar, which are worksheet tables; in this case, order headers and lines.

Tables in SCM have a property that defines the type of table, and each type is associated with a particular style of form for the user interface. We could, therefore, consider these types as patterns. If we think of them as patterns, it is far easier to apply the recipes to our own development.

The following list is of the common table types, listed with the usual form design and the typical usage:

Table group	Form design pattern	Usage
Miscellaneous	None	This is essentially "undefined" and shouldn't be used, other than for temporary tables.
Parameter	Table of contents	This is used for single-record parameter forms.
Group	Simple list Simple list and details-ListGrid	This is used for the backing table for drop-down lists. The Simple list design pattern is suitable for when only a few fields are required; otherwise, the Simple list and Details patterns should be used so the fields are presented in a useful way to the user.
Main	Details Master	This is used for main tables, such as customers, suppliers, and items.
Transaction header Transaction Line	Simple List and Details with standard tabs	This is used for datasets, such as the invoice journal form, which contain posted transactional data with a header and lines.
Transaction	Simple List and Details w/ standard tabs	This is used for tables, such as the inventory transaction form, which contain posted transactional data but at a single level.
Worksheet header Worksheet line	Details transaction	This is used for data entry datasets, such as the purchase order, where the dataset is made up of header and line tables. The pattern has two views, a list view of header records, and a detail view where the focus is the lines.
Worksheet	Details Master	This is a single-level data entry dataset, which is rarely used in SCM.

In this chapter, we will create types and tables for the common types of table, but we will complete the patterns when we cover the user interface in Chapter 3, Creating the User Interface.

In this chapter, we will cover the following recipes:

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

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

By : Simon Buxton

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

By: Simon Buxton

Overview of this book

Related Content you might be interested in

Current Title:

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

Dynamics 365 for Finance and Operations Development Cookbook

Implementing Microsoft Dynamics 365 for Finance and Operations Apps

Implementing Microsoft Dynamics 365 for Finance and Operations