Attribute(s)
Naming Convention
Description
General Naming Conventions - View names are at the discretion of the designer. There are, however certain guidelines that must be followed. These are described in the Details field.
Motivation
Views are vital design elements, seen by users and referenced regularly in formulas. Therefore, some standards regarding naming conventions must be developed.
Example / Details
While view names are largely left to the discretion of the designer, the
following rules should be observed:View names must be descriptive and indicate the function of the view.
e.g. Incorrect Correct
All Docs All Main Topic Documents
Numbers should be used to order the views, making them more intuitive for the
users.
The second level of ordering should be arranged through the use of letters.
Where possible, view names should be cascaded to save screen space in the view
pane:
1. All Documents\ a. By Author
1. All Documents\ b. By Subject
Views should conform to the following general order of appearance:
All Documents available to the user.
Subsets of Documents based on different selection criteria.
Administrative views, visible only to database administrators and information
owners.
Views with identical functions in different databases should have the same name.
Views that are used for lookup functions (@DbLookup or @DbColumn) should have a
name beginning with '(Lookup\....)'. These views must at all times be hidden.
Any views accessed by a @Picklist formula should have a name beginning with
'(Picklist\....) '. These views must at all times be hidden.
Note: All hidden views can be seen by pressing Ctrl + Shift as you open the
database.