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 layered model

We have built an application in four steps by implementing Architectural Patterns and adding Design Pattern elements.

This allows us to look at our model from a top-down perspective, as shown in the following figure:

The entries are the heart of our application that act for analysis and reporting. They are related to Master Data, the people we do business with and the products we use. Journals allow us to implement rules and manage transactions. Documents are the workflow elements that allow people to use the application in a way that makes sense.

In Microsoft Dynamics NAV, this model has one extra layer, the processes, that we've out scoped in this chapter for reasons of simplicity.

For the processes that have multiple documents related and/or more static, Dynamics NAV has processes. From a Pattern perspective, they use the same elements as Master Data.