Programming Microsoft Dynamics NAV - Fifth Edition
by Marije Brummel, David Studebaker, Christopher D. Studebaker
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 ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access