Book Image

Learning Dynamics NAV Patterns

By : Marije Brummel
Book Image

Learning Dynamics NAV Patterns

By: Marije Brummel

Overview of this book

Microsoft Dynamics NAV is a complete ERP system, which also contains a robust set of development tools to support customization and enhancement. These include an object designer for each of the seven application object types, a business application-oriented programming language with .NET interface capability, a compiler, a debugger, and programming testing language support. Learning Dynamics NAV Patterns will guide you through the NAV way of solving problems. This book will first introduce you to patterns and the software architecture of the NAV and then help you to build an example application. Then, it walks you through the details of architectural patterns, design patterns, and implementation patterns. This book will also talk about anti-patterns and handling legacy code. Finally, it teaches you to build solutions using patterns. Proven patterns and best practices will help you create better solutions that are easy to maintain in larger teams across several locations. It will guide you through combining abstract patterns using easy-to-understand examples and will help you decide which patterns to use in which scenarios.
Table of Contents (9 chapters)
Thank you for buying Learning Dynamics NAV Patterns

Document History

In Microsoft Dynamics NAV, Documents have a limited life cycle and once obsolete, they need to be removed from the table. The Document History pattern helps us to create this. Examples of historical documents are Sales Order Archive, Sales Shipments, Invoices and Credit Memos. Issues Reminders, and Service Invoices. They act as data containers, and are often used to print documents. Once the documents are printed, they can be deleted.

An explanation of how to read and understand posting routines in Microsoft Dynamics NAV is available at

Technical description

When creating History for a Document, we move the data from one set of Document tables to another. This is done using a number of Codeunit objects.

The naming conventions

From a functional perspective, this process has many names, such as Posting, Archiving, Issuing, and Registering. This term is...