Microsoft Dynamics NAV - C/SIDE Solution Development -

Microsoft Dynamics NAV – C/SIDE Solution Development

Locus IT ServicesMicrosoft Dynamics NAV – C/SIDE Solution Development

Lesson 2: Standard Data Model

Standard Data Model

Every application area in Microsoft Dynamics NAV follows the same principles and has a similar data model. Master, subsidiary, document tables, journal, ledger, and other tables all have the same role. There are certain patterns that are applied consistently across all application areas.

Depending on their types, there are certain code patterns that you can follow in all tables of the same type.

The consistency of data model and data flow patterns is important for both users and developers. When users master one application area and understand data model principles, they can also quickly understand other application areas. As a developer, when you understand the principles of data models and patterns, you can customize the standard application. You can also build new application areas and maintain a consistent experience in the standard application. This makes sure that users are as productive as possible.

Typical Data Triggers

In addition to maintaining data validity through data types and table relationships, Microsoft Dynamics NAV also contains data-related business logic. This makes sure that more complex data-related business rules are consistently applied as users insert, change, or delete information in the database.

These complex business rules are coded in table triggers as C/AL code. You can find the same patterns of code in the same types of tables, regardless of the application area where they belong.You must understand these principles, and make sure that the code that you write in the existing objects does not violate those principles. You must also apply the same principles when you create completely new application areas.

OnInsert Trigger

This table trigger executes when a user inserts a new record into a table. The code in the trigger executes before the record is actually inserted into the table. If the code in the trigger causes a run-time error to occur, then the insert operation is canceled.

Locus IT Project Management Office
What’s it?