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

The Supplemental and Subsidiary Pattern

For Microsoft Dynamics NAV to run properly, we also require tables that contain more records to allow multiple values to be used in various scenarios. These values are almost as static as the Singleton tables, although the new records can be created during the lifecycle of the application.

The pattern for these tables is Supplemental & Subsidiary.

Technical description

The Supplemental & Subsidiary table has a single field Primary Key that is typically called Code; it has the Data type code, and has a length of 10 characters. Values in the Primary Key are manually determined by the application administrators. Normal users of the system have read-only access to these tables.

When the attributes in the table relate to another entity, the reference to this entity can be added as a second primary key.

The referenced entity is typically of the Master Data pattern. We will discuss Master Data later in this chapter.

The other...