Book Image

Extending Microsoft Dynamics NAV 2016 Cookbook

By : Alexander Drogin
Book Image

Extending Microsoft Dynamics NAV 2016 Cookbook

By: Alexander Drogin

Overview of this book

Microsoft Dynamics NAV is an enterprise resource planning (ERP) software suite for organizations. The system offers specialized functionality for manufacturing, distribution, government, retail, and other industries. Its integrated development environment enables customizations with minimal disruption to business processes. The book starts explaining the new features of Dynamics NAV along with how to create and modify a simple module. Moving on, you will learn the importance of thinking beyond the boundaries of C/AL development and the possibilities opened by with it. Next, you will get to know how COM can be used to extend the functionalities of Dynamics NAV. You’ll find out how to extend the Dynamics NAV 2016 version using .NET interoperability and will see the steps required to subscribe to .NET events in order to extend Dynamics NAV. Finally, you’ll see the cmdlets available to manage extension packages. By the end of the book, you will have the knowledge needed to become more efficient in selecting the extending methods, developing and deploying them to the Dynamics NAV, and practicing the best practices.
Table of Contents (17 chapters)
Extending Microsoft Dynamics NAV 2016 Cookbook
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Working with single instance codeunits


A single instance codeunit is an implementation of the singleton design pattern, an object that can be instantiated only once; all application objects referring to the singleton will reuse the same instance throughout the application.

Typically single instance codeunits are used to store an instance of an external dotNet component that cannot be instantiated twice, such as the Outlook application. Another example of a singleton object is a storage of user settings data, received from an external source.

How to do it...

In this recipe we will use a single instance codeunit to store user configuration read from an XML file. Configuration will include default date range for the Item Profit page used to report profits per item. This page is described in detail in the Simplifying data access with queries recipe.

  1. Create a table in the object designer. The table will be used as temporary data source and won't store anything in the database.

  2. Create tree fields in...