Naming tables

There are standardized naming conventions defined for NAV, which we should follow. Names for tables and other objects should be as descriptive as possible, while keeping to a reasonable length. This makes our work more self-documenting.

Table names should always be singular. The table containing data about customers should not be named Customers, but Customer. The table we created for our WDTU Radio Station NAV enhancement was named Radio Show, even though it will contain data for all of WDTU's radio shows.

In general, we should always name a table so it is easy to identify the relationship between the table and the data it contains. For example, two tables containing the transactions on which a document page is based should normally be referred to as a Header table (for the main portion of the page) and a Line table (for the line detail portion of the page). As an example, the tables underlying a Sales Order page are the Sales Header and the Sales Line tables. The Sales Header table contains all the data that occurs only once for a Sales Order, while the Sales Line table contains all the lines for the order.

Additional information on table naming can be found in the old, but still useful, C/AL Programming Guide, which can be found on the Mergetool.com site at http://www.mergetool.com/oldmergetool/CalProgGuide.pdf. These older documents may be obsolete in some areas. So, of course, we should always refer first to the Developer and IT Pro Help included in NAV and accessible from the Development Environment. The NAV 2017 Help is also available on MSDN at https://msdn.microsoft.com/en-us/dynamics-nav/index.

Table of Contents for Naming tables

Create new playlist

Sign In

Sign Up

Table of Contents for
Naming tables