Microsoft Dynamics NAV - C/SIDE Solution Development -

Microsoft Dynamics NAV – C/SIDE Solution Development

Locus IT ServicesMicrosoft Dynamics NAV – C/SIDE Solution Development

Lesson 3: Reviewing the Table Code

Reviewing the Table Code

Reviewing the Table Code : In Microsoft Dynamics NAV 2013, transactional tables, including document tables, always include lots of code. You have already reviewed the Seminar Registration Header table. Now review other tables that you imported.

Most of the code in transactional tables is specific to the transaction that the table supports. But there are frequently many patterns that you can recognize in many other transactional tables. Price calculations for discounts or conversions between different units of measures are several concepts that behave in the same manner. There are many more patterns and concepts that you will recognize if you review the transactional tables in Microsoft Dynamics NAV 2013. When you develop a solution that involves those concepts, you can apply the solution patterns that are present in many standard tables.

Demonstration:  Reviewing the Seminar Registration Line Table Code

Document tables are frequently full of code that runs business logic to safeguard the integrity of the document transactions. Many fields in document tables populate the default values from different master records into other fields, run various types of validations, or call operations such as amount, discount, unit of measure, VAT, and other types of calculations.

Reviewing the business logic of the Seminar Registration Line table helps you understand the kind of business logic that you must add to any document line tables that you develop.

Demonstration:  Reviewing the Seminar Charge Table

Many tables in Microsoft Dynamics NAV 2013 frequently relate to several other tables from the same field. This concept is known as conditional relationships. These are relationships where one field relates to several tables that are based on the value of another field. For example, the No. field in the Sales Line table relates to several tables based on the value of the Type field. When these relationships are used, there are several patterns that you can see in the existing tables. Apply these patterns to your custom tables to maintain a consistent user experience across the application.

The Seminar Charge table also uses the conditional relationship concept by relating to the G/L Account and Resource tables from the No. field, based on the value that is specified in the Type field.

Locus IT Project Management Office
What’s it?