Collection-oriented Task Pages
In Microsoft Dynamics NAV, collection-oriented task pages are used to support users when their tasks involve multiple entities or records at the same time. The most typical collection-oriented task page is the list (showing customers, items, etc.) from which the user can seek out particular entities to work with.
Collection-oriented page characteristics
The overall characteristics of a collection-oriented task page include:
A prominent list or grid of entities, records, or entries.
A page title, or alternatively fields above the grid/list, which describe or identify the collection of data shown in the page. For example, the Customer List provides an overview of the customer entities from which the user can then open individual customer card pages.
Ribbon commands that act with regard to the selected row or rows in the list or grid. For example, selecting a particular customer in the Customer list, and then choosing Delete from the ribbon, will delete only the selected customer, not all customers in the list.
You use the Microsoft Dynamics NAV Development Environment to develop and customize pages for your solution’s needs. The UX guidelines for designing collection-oriented pages are organized into page templates. Each page template represents a recommended way to design pages for a particular type of user task.
We recommend designing pages according to the suggested templates and following the associated guidelines. Design a custom style of page only when your application has special requirements that are not met by the standard page templates.
Collection-oriented page templates
| Standard page template | Usage characteristics | Page object contents/properties |
|---|---|---|
A list that is editable either in-line or via a details sheet. Well-suited for tasks related to managing simple entities having only few fields. For example, reference data such as Post Codes. |
A page object of type List with the Editable property set to Yes, and having fields in a Repeater group. |
|
A list for providing an overview and finding specific entities/entries to work with. Adding, removing, and editing lines in the list take place via a separate page or a details sheet, not in-line. |
A page object of type List with the Editable property set to No, and having fields in a Repeater group. |
|
A grid for providing an overview and managing data in tabular or matrix form. The grid has associated fields where the user can specify filtering, or specify the default values for fields to be effective during data entry and editing in the grid. |
A page object of type Worksheet with a field or a group of fields, such as filters, followed by a Repeater group that has fields representing the columns in the grid. |
|
A type of worksheet for journal line data entry and editing, before committing or posting. The grid has an associated field (typically displayed above) where the user can switch between journal batches. |
A page object of type Worksheet with a field to represent the journal batch, followed by a Repeater group that has fields representing the columns in the grid. |
|
A type of worksheet for working with results of inquiries or calculations. The grid has associated fields where the user provides criteria and parameter values for processing. |
A page object of type Worksheet with a field to represent the journal batch, followed by a Repeater group that has fields representing the columns in the grid. |
For all collection-oriented task page templates, you can choose to add the following additional page elements:
Ribbon actions by which the user can act on the selected row in the grid or list, or navigate to related pages and reports.
FactBoxes that show related details (statistics, links, notes) about the selected row in the grid or list, in textual or chart form.
A Details pane below the grid or list can show details (additional fields) about the selected row, in textual or chart form.
In addition, some page templates can contain fields for filtering, for default values, and so on.