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 Argument table

The Argument table has an ambiguous place in the categorization of patterns. The table is used to combine fields when we call a function. This can be compared to a class in object-oriented programming. Since Microsoft Dynamics NAV does not allow us to create a class, we use the table object instead. This will automatically create a table in the SQL Server, but this table will never contain any data. However, some tables are used for both arguments and normal data.

In computer programming, the general rule of thumb is to avoid functions that have too many arguments in the signature. When a function has more than three or four arguments, we should combine them into an argument table.

Technical description

The definition of the table should contain all the fields used in the arguments. The primary key of the table is not important, since the table will never contain actual data. However, the metadata in Microsoft Dynamics NAV requires at least one field as...