Implementing Dynamics NAV 2013: architecture & philosophy

Knowing the Dynamics NAV philosophy of how things are done is important
for everyone.

It is important for users and people working in a company that uses or will use
Dynamics NAV as their ERP. They have to know how to do things and, especially,
be aware of the consequences of what they do.

It is also important for consultants, analysts, and developers, for people working in
a company that implements Dynamics NAV, and for partners. They have to fully
understand the way NAV works, not only because they are the people responsible
for transmitting that knowledge to users, but also because they will probably be
designing and developing new functionalities or modifying existing ones. For this, it
is important to use the same structures, way to present data, way to make information
flow, and, in the end, the same philosophy Dynamics NAV uses in all its standard
functionalities. Completely different behaviors may confuse your end users

Chapter 3 of the book Implementing Microsoft Dynamics NAV 2013 covers:
– The structure of Microsoft Dynamics NAV 2013, the data model
– The way information flows in Microsoft Dynamics NAV 2013 (journals, posting routines and so on)

You can get a copy of the book here:

If you have any doubt or you want to get more information, I will answer your questions.

As an example of what the chapter covers:
The following diagram shows the existing journals, its relations, and the entries that are created after them:

Navision 2013 Journals



Laura Nicolàs

Author of the book Implementing Microsoft Dynamics NAV 2013