Skip to content

Latest commit

 

History

History
122 lines (80 loc) · 4.33 KB

File metadata and controls

122 lines (80 loc) · 4.33 KB
title description author ms.author ms.topic ms.date ms.reviewer audience ms.search.region ms.search.validFrom ms.dyn365.ops.version ms.assetid
Toolbar and List subpattern
Learn about the Toolbar and List form subpattern, including overviews on usage, wireframes, models, UX guidelines, and examples.
jasongre
jasongre
article
06/20/2017
johnmichalak
Developer
Global
2016-02-28
AX 7.0.0
a60f829b-e496-453b-9e58-f7cb4d67114f

Toolbar and List subpattern

[!include banner]

This article provides information about the Toolbar and List form subpattern. This subpattern is used to show child collections for the parent entity as either a tabular grid or a tree.

Usage

This subpattern is used to show child collections for the parent entity as either a tabular grid or a tree. The toolbar contains fewer than 10 actions. If a grid is used, it contains fewer than 10 fields. This article describes two patterns:

  • Toolbar and list – This is the basic version of the pattern and should be used by default.
  • Toolbar and list (double) – This variant includes two lists and an optional toolbar above each list.

Wireframes

Toolbar and list

Wireframe for Toolbar and List form.

Toolbar and list (double)

Wireframe for Toolbar and List (double) form.

Model

Toolbar and list – High-level structure

  • [Container]

    • Toolbar (ActionPane, Style=Strip) [Optional]
    • CustomFilterGroup (Group) [Optional]
    • Grid | Tree | ListView | Table
    • Footer (Group) [Optional]

Toolbar and list (double) – High-level structure

  • [Container]

    • Toolbar1 (ActionPane, Style=Strip) [Optional]
    • CustomFilterGroup1 (Group) [Optional]
    • Grid | Tree | ListView | Table
    • Toolbar2 (ActionPane, Style=Strip) [Optional]
    • CustomFilterGroup2 (Group) [Optional]
    • Grid | Tree | ListView | Table
    • Footer (Group) [Optional]

Core components

  • Apply the ToolbarList subpattern to a container control.
  • Address BP Warnings:
    • Grid.DataSource must not be empty.
    • No additional BP checks are required beyond the AX6.3 BP checks that were carried forward.

Related patterns

UX guidelines

The verification checklist shows the steps for manually verifying that the form complies with UX guidelines. This checklist doesn't include any guidelines that will be enforced automatically through the development environment. Open the form in the browser, and walk through these steps.

Standard form guidelines:

Toolbar guidelines:

Examples

Toolbar and list

Form: VendTable (TabCommunication)

Toolbar and List example.

Toolbar and list (double)

Form: SalesQuickQuote (TabPageExistingItems)

Toolbar and List (double) example.

Resources

Typically used by patterns

Appendix

Frequently asked questions

This section will have answers to frequently asked questions that are related to this guideline/pattern.

Open issues

  • Does CommandButton.Command contain Add and Remove actions that provide the default icon, label, and tooltip?
    • Not yet. Deliverable 1052359 will look at setting these defaults for Add and Remove commands.
  • Do we care about separators between groups of icons in a migration context?
    • Currently, we don't show separators between button groups on toolbars.

Microsoft Dynamics AX 2012 content

VendTable

Previous version example.

[!INCLUDEfooter-include]