Form Types

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Microsoft Dynamics AX 2012 provides form types that allow users to perform tasks in a consistent manner. The Microsoft Dynamics AX 2012 client uses the following forms.

Form type	Primary work patterns	Usage examples
Entity details	View and edit master data* Other uses: View and edit line item details Editable list	View customer information Create a new vendor Create a project Create a catalog View and edit line item details
Source documents	Detail forms for viewing and editing Other uses: View and edit line item details Editable list	Purchase requisition Purchase order Sales order Packing slip Invoice Payment
Journal	Data entry in a grid Other uses: View Journal information and lines	Payment journal Payment journal vouchers
Simple list and details	View and edit reference and dependent data	ZIP Codes Currencies Employee contacts Miscellaneous charges
Table of contents	Configure data in a multi-step pattern or free-form	Accounts payable parameters Address format
Inquiry	View related data	Invoice journal inquiry
Dialog	Secondary window that allows commands and questions, and provides information or progress feedback	Create transactions Submit to workflow Confirm delete action Workflow actions such as Submit, Approve, Reject, and Request change Two-phase create Activity tasks
Drop dialog (Also called a quick path)	Lightweight dialog that displays a small set of options specific to an action or confirms an action without using a full dialog	Process hold Set date effective options

* Document data mostly appears in edit mode, which is used for editing entities that reference data from other tables, for example, Project, which pulls in resources, categories, and so on. Typically, the user will need to spend several hours creating the document, coming back to edit it many times over a long period of time, which is different from transient entities, such as sales orders.

Glossary

Term	Definition
Master data	Data that is generally persistent over time and that represent the items that are important to track in the ERP system. Master data is the nouns of the system, such as Customers, Vendors, Sales people, and Employees.
Source documents	Business events generated from the occurrence of an economic transaction are documented on source documents and recorded in accounting journals when the source document is journalized. Transactions will generally affect master data and make use of reference data and parameters.
Reference data	Reference data is data that is used by both master and transaction data. Reference data is found in the setup areas of the system and is fairly stable over time.
Dependent data	Dependent data is data that is associated with master data, transaction data, and reference data. Dependent data is generally deleted when the parent is deleted. In UML, dependent data is a composition relationship.

Form examples

Example of a details form

Example of a details form

Example of an editable list form

Example of an editable list form

Example of a journal form

Example of a journal form

Example of a simple list and details form

Example of a simple list and details form

Example of a table of contents form

Example of a table of contents form

Example of an inquiry form

Example of an inquiry form

Example of a wizard form

Example of a wizard form