Book Image

Extending Microsoft Dynamics 365 for Operations Cookbook

By : Simon Buxton
Book Image

Extending Microsoft Dynamics 365 for Operations Cookbook

By: Simon Buxton

Overview of this book

Dynamics 365 for Operations is the ERP element of Microsoft’s new Dynamics 365 Enterprise Edition. Operations delivers the infrastructure to allow businesses to achieve growth and make better decisions using scalable and contemporary ERP system tools. This book provides a collection of “recipes” to instruct you on how to create—and extend—a real-world solution using Operations. All key aspects of the new release are covered, and insights into the development language, structure, and tools are discussed in detail. New concepts and patterns that are pivotal to elegant solution designs are introduced and explained, and readers will learn how to extend various aspects of the system to enhance both the usability and capabilities of Operations. Together, this gives the reader important context regarding the new concepts and the confidence to reuse in their own solution designs. This “cookbook” provides the ingredients and methods needed to maximize the efficiency of your business management using the latest in ERP software—Dynamics 365 for Operations.
Table of Contents (16 chapters)

Introduction

Workflow in Microsoft Dynamics 365 for Operations have two main types of element, approvals and tasks, centered on a document. This is the center of the workflow where tasks are triggered based on what the user decides. By a document, it means 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 the tables used in the workflow in order to decide what happens. This solves many requirements where a great deal of configurability is required, but can also be misunderstood and used inappropriately. The submission of a workflow is usually started with the user pressing a Submit button on the form, which is then processed within a minute by the batch server. The minimum time it can take for a workflow to complete...