Book Image

Learning Dynamics NAV Patterns

By : Mark Brummel, Marije Brummel
Book Image

Learning Dynamics NAV Patterns

By: Mark Brummel, 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.

Related Content you might be interested in

Current Title:

Small book image
Learning Dynamics NAV Patterns
Mark Brummel | Marije Brummel
Sep, 2015 | 214 pages
No titles found
Table of Contents (9 chapters)
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
Chapter 1: Introducing Dynamics NAV Patterns and Software Architecture
Chapter 1: Introducing Dynamics NAV Patterns and Software Architecture
What do we mean by 'patterns'?
Microsoft Dynamics NAV Design Patterns
Patterns elements and hierarchy
Building blocks
Metadata
Base application
Summary
2
Chapter 2: Architectural Patterns
Chapter 2: Architectural Patterns
The Singleton Pattern
The Supplemental and Subsidiary Pattern
The Compound Pattern
The Rules Pattern
The Master Data Pattern
The Journal Template-Batch-Line Pattern
The Entry Pattern
Document Pattern
The Argument table
Summary
3
Chapter 3: Design Patterns
Chapter 3: Design Patterns
The Entity State Pattern
The Select Pattern
The Number Series Pattern
Address Integration Pattern
Multi-Level Setup
Document History
Copy Document Pattern
Job Queue Entry Pattern
Dismissible dialogs and save preferences
Setup Update Pattern
Model-View ViewModel Pattern
Summary
4
Chapter 4: Building an Example Application Using Patterns
Chapter 4: Building an Example Application Using Patterns
The design elements
The Pattern dependencies
Step one – Foundation
Step two – Master Data
Step three – Journals & Entries
Step four – Documents
The layered model
Summary
5
Chapter 5: Coding Best Practices
Chapter 5: Coding Best Practices
Coding guidelines
Class-Method-Property
Function libraries and interfaces
Natural Language Programming
Encapsulation
Façade
Hooks
Variant variables
Managing DLL
Summary
6
Chapter 6: Anti-patterns and Handling Legacy Code
Chapter 6: Anti-patterns and Handling Legacy Code
Anti-patterns
Legacy code
Refactoring the C/AL Code
The boy scout rule
Summary
7
Chapter 7: Building Solutions Using Patterns
Chapter 7: Building Solutions Using Patterns
Building blocks
Creating the Table objects
Applying Design Patterns
Defining the methods
Writing the Code and Link methods
Refactoring
Testing the application
Upgrading the application
Building our application
Managing the source code
Summary
8
Thank you for buying Learning Dynamics NAV Patterns
About Packt Publishing
About Packt Enterprise
Writing for Packt

Class-Method-Property

The Microsoft Dynamics NAV Development Environment allows us to write code in almost any place within the application. Each object has dozens of triggers that allow writing C/AL code.

If we just write bits and pieces of code everywhere in the objects, the maintainability of the application would be hard for anyone, including the original developer.

To write code in such a way that other developers can find their way requires a set of rules. If we apply these rules, it will be easier for others to see what we did, because we will reduce the number of places where we write business logic.

The Table as a class

Before we start coding, we need to find the owner of a process. If we explicitly connect the process to the owner, it will be easier for everyone who works with the object to understand what it can do.

Let's try to clarify this with an example. One of the processes that has a lot of owners in Microsoft Dynamics NAV is printing an address...

Previous Section
End of Section 3
Next Section