Page names

Card pages are named similarly to the table with which they are associated, with the addition of the word "Card". For example, Customer table and Customer Card, Item table and Item Card, Vendor table, and Vendor Card.

List pages are named similarly to the table with which they are associated. List pages that are simple noneditable lists have the word "List" associated with the table name; for example, Customer List, Item List, and Vendor List. For each of these, the table also has an associated card page. Where the table has no associated card page, the list pages are named after the tables, but in the plural format. For example, Customer Ledger Entry table and Customer Ledger Entries page, Check Ledger Entry table and Check Ledger Entries page, Country/Region table and Countries/Regions page, Production Forecast Name table and Production Forecast Names page.

The single-record Setup tables that are used for application control information throughout NAV are named after their functional area, with the addition of the word "Setup". The associated Card page should also be, and generally is, named similarly to the table. For example, General Ledger Setup table and General Ledger Setup page, Manufacturing Setup table and Manufacturing Setup page, and so on.

Journal entry (worksheet) pages are given names tied to their purpose, with the addition of the word Journal. In the standard product, several Journal pages for different purposes are associated with the same table. For example, the Sales Journal, Cash Receipts Journal, Purchases Journal, and Payments Journal all use the General Journal Line table as their Source Table (they are different pages all tied to the same table).

If there is a Header and Line table associated with a data category, such as Sales Orders, the related page and subpage ideally should be named to describe the relationship between the tables and the pages. However, in some cases, it's better to tie the page names directly to the function they perform rather than the underlying tables. An example is the two pages making up the display called by the Sales Order menu entry--the Sales Order page is tied to the Sales Header table, and the Sales Order Subform page is tied to the Sales Line table. The same tables are involved for the Sales Invoice page and Sales Invoice Subform page.

The use of the word Subform rather than Subpage, as in Sales Invoice Subform, is a leftover from previous versions of NAV, which had forms rather than pages. We are hopeful Microsoft will eventually fix this historical artifact and rename these pages as Subpages.

Sometimes, while naming pages, we will have a conflict between naming pages based on the associated tables and naming them based on the use of the data. For example, the menu entry Contacts invokes a main page/subpage named Contact Card and Contact Card Subform. The respective tables are the Contact table and the Contact Profile Answer table. The context usage should take precedence in the page naming as was done here.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.16.147.124