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

Function libraries and interfaces

Not every function in Microsoft Dynamics NAV has a clear owner. In some cases, we have a function that can be accessed using simple variables that perform some calculation or a small piece of business logic.

These functions can be put in function libraries or interfaces. By doing this, it is easy for other developers to reuse them.

Examples of function libraries can be string manipulations or date functions. Microsoft Dynamics NAV does not have a lot of built-in functions for this, and many developers have created their own collection of functions through the years.

An Interface is a reusable component that can be accessed from anywhere in the application. A very good example of what could and should be an interface is the function called DateNotAllowed in Codeunit 11, Gen. Jnl.-Check Line:

IF (AllowPostingFrom = 0D) AND (AllowPostingTo = 0D) THEN BEGIN