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 Pattern

The EARP systems are traditionally designed to help companies administer the paper trail, required to run their businesses, often from a legal perspective. To be able to register the paper documents in an electronic form, Document Pattern can be used.

Technical description

The Document pattern allows us to enter a header and line information. The header information is often related to Person Master Data (with whom I am doing business), whereas the lines are of the type Product (the kind of business that I am doing).

Each Document Pattern has two tables: a header and line. These names are important, the Sales Header and the Sales Line tables follow this convention, just as others.

The Header table

The header table has a primary key that is called No., and has a type Code with a length of 20 characters. Optionally, the primary key can also contain a reference to a normalized document type. Normalized in this case means that the share tables and business...