Overview form patterns

In D365 FO the concept of form patterns is introduced. At the form Design, when doing a right mouse click, dialog with the option ‘apply pattern’ appears. Here we see the available patterns. Each pattern has it’s own characteristic/ properties. In this post I will describe the main patterns.








1.Details Master

Pattern is used for view, edit and also for entering data. Typical characteristic of this pattern are the fast tabs. There is the basic version and with standard tabs (>15 fasttabs). User can switch between, header and line view. Details master is typically used for display of masterdata for example CustTable, VendTable or product variants (EcoResProductVariants) forms.

Details Master design







Details Master grid view






Detail Master form design: mandatory form controls
Details Master details view (to switch from grid view to details view select any record in the grid to switch)

















2. Detail Transaction

Usually a form with this pattern consists of both header and details grid/ lists, based on different data sources like parent child. User is able to switch between, header and line blocks.








PurchTable form is an example of a form with a Detail Transaction pattern








3. Listpage

Used for search, filter and browsing records which are displayed in a grid.








Example of a form with a ListPage pattern is the InventOnHandItemListPage







4. Simple List

Displays relatively simple information, usually less than 6 fields for single tables.








Vendor group form is an example of a form with a Simple List pattern








5. Simple List and Details – List grid

If in the form there are more than 6 fields and/or more than one data source this pattern is used.









Form AssetConsumption factor is an example of a form with a Simple List Details pattern








6. Task Single and Task Double

Is not best practice to create new forms with this pattern.








7. Table of Content

Used when more data sources are used for setup configuration for example a module, for example parameters for a module.








InventParameters is an example of a form with a Table of content pattern








8. Wizard

Used for guiding the user through multiple pages for completing a task.








The first page is the welcome screen (WMSLocation wizard). When clicking ‘next’ button the wizard moved to the next page








This is the second page of the wizard. The next button is disabled because not all mandatory information is entered.








9. Workspace Operational

Used for navigation to tasks and specific pages. Characteristic of this pattern is that there is no data source in the form.









AssetWorkspace is an example of a form with this pattern