O'Reilly logo

Microsoft Dynamics NAV by Mark Brummel, Christopher Studebaker, David Studebaker, David Roys, Vjekoslav Babić, Cristina Nicolàs Lorente, Laura Nicolàs Lorente, Alex Chow

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

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

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 ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required