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)

Applying metadata fixes

Metadata fixes are updates to the source code of Operations. For over-layering we would use the These are used to code-merge over-layered code, but they are still needed on extension projects as this is part of the process to push updates downstream to the build, test, and eventually, the production environment.

The process of applying the updates is straightforward; it is the process that is the most important aspect to take away from this.

LCS can see which metadata fixes are available for each environment connected to the project. When working on a customer implementation project, use the Sandbox (test) environment as the reference VM to check for updates. When working on internal or ISV projects, use a reference VM hosted in Azure for this. On-premise implementations will be connected to LCS and will be handled in the same way as Azure-based implementation projects.

The cycle is as follows...