Best Practices for Views
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
This topic contains information about the best practices for setting view properties and view field properties.
View Properties
The properties that are available for views are a subset of the properties available for tables. Views are read-only, and so some of the properties are set by default and cannot be changed. Best practices are listed for some of the properties that can be edited:
Property |
Rules |
|---|---|
Name |
Cannot have same name as a class, table, map, enum, or data type. Prefix with the module name, for example: Cust, Ledger, Proj. Infix with a logical description of contents, for example ProjCommittedCostCategoryView, where "ComittedCostCategory" is the infix. You can use 'View' as a postfix. |
Label |
Mandatory property. The text value of the Label must be unique across all tables, views, and maps, in all languages. |
TitleField1, TitleField2 |
TitleField1 is the title that is used on forms that use the view as main datasource. TitleField2 is the secondary title and is used on forms that use the view as main datasource. |
AnalysisVisibility, AnalysisSelection, TypicalRowCount, IsLookup, SingularLabel |
These properties are inherited from tables, where they are used as part of the end-user reporting system. End-user reporting is not implemented for views, and so any best practice errors about these properties should be ignored for views. |
View Field Properties
Many of the properties that are available for view fields are also available as properties on table fields. The best practice advice is the same as for table field properties.
See also
Best Practices for Table Field Properties
Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.