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

Step two – Master Data

When you decide to use Microsoft Dynamics NAV as a platform to build new applications, it is very likely that your application has a close resemblance to the ERP software. This is what Dynamics NAV was originally designed to do best, and the Meta Data elements are also optimized to work as such.

Within the ERP applications, we typically have Master Data that resembles people or things. In our example application, we will call them Example Person and Example Product.

The Master Data pattern schema is shown in the following diagram:

Example Person

For our Example Person entity, we need to create a table that contains the elements of our Pattern. We will call our table called Example Person, and save it with an ID of 50010.

Leaving a small gap in the field and table IDs in our module gives us the option of later adding other tables in between, if this makes sense from a perspective of grouping similar objects together...