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)

Extending standard tables without customization footprint

Table extensions provide a way to add fields to a table without over-layering. This means that we don't need to perform a code merge when the base package is changed.

In this recipe, we will add a field to the SalesConfirmHeaderTmp table, which we will use in the How to customize a document layout without an over-layer recipe.

It is common to have the main development work in one package, and reports in a higher package, as this can help with deploying updates. When deciding which package this table extension should be done in, we need to consider the scope of its usage should be. If we create the additional fields in a reporting package, which references a main development package, the main development package will not be able to use this field.

Sometimes a report drives the requirement for additional fields. So, it can seem natural to add the new fields...