Detail AOT objects

The Application Object Tree (AOT) contains all the application objects used to build Microsoft Dynamics AX, such as the classes, tables, forms, and so on.

To create a new object in the AOT, right-click the relevant node, and then click New. In addition, drag-and-drop operations are available for many application objects, including table fields.
The AOT contains the nodes described in the following table below. All nodes have the following:

• Properties. To see the properties of the current node, right-click the node, and then click Properties.

Node	Description
Data Dictionary	Contains the data types and tables that make up your database. Also contains objects to control access to the data. It contains the following subnodes: Tables: Tables that contain the Microsoft Dynamics AX data. Maps: Enables you to create associations between closely related (but non-identical) table fields and methods. Views: Enables you to join data from different tables, and then to select which fields you want to display. Extended Data Types: Data types that extend one of the primitive data types or another extended data type. Base Enums: Enumerable types that contain a list of literals. License Codes: Determines which components of Microsoft Dynamics AX functionality are available to a company. Configuration Keys: Allows administrators to enable or disable features in the application for all users. Security Keys: Allows administrators to set security on a user group level. Table Collections: Collections of tables that contain data that is often shared between companies. Perspectives: Collections of tables used to organize information for report models.
Macros	Contains the source code for the macros used by the standard application. In addition to viewing the existing code, you can add your own macros.
Classes	Contains the source code for the application (X++) classes. You can also use system classes (also known as kernel classes). They are listed in the System Documentation\Classes node.
Forms	Dialogs that are the user's interface to the database.
Reports	Enables users to print or display summary information from the database.
Queries	Used as the source of records for forms and reports.
Jobs	Typically holds small X++ programs that are used to test new code.
Menus	Contains the menus you want the end user to see.
Menu Items	Contains a complete list of the items that can be presented in a menu.Menu items act as a layer of abstraction above forms, reports, and so on.
Web	Contains objects related to Web development.
Resources	Contains references to image and animation files.
References	Contains references to Microsoft .NET assemblies that are referenced in X++ statements.
System Documentation	Contains items that represent system (kernel) classes, functions, tables, and so on. This node also contains links to the documentation for these items.
Application Developer Documentation	Contains links to the reference documentation for application tables and classes.
Application Documentation	Contains links to the reference documentation for Microsoft Dynamics AX end users.
HTML Help Files	Contains references to the collections of .chm files that are used to provide developer, administrator, and end-user Help for Microsoft Dynamics AX.

What is AOT

Application Object Tree(AOT)

The AOT is the main entry point to MorphX and is the repository explorer for all metadata. You can open the AOT by clicking the AOT icon on the toolbar or by pressing Ctrl+D. The AOT icon looks like this:

Navigating the AOT

As the name implies, the AOT is a tree view. The root of the AOT contains the element categories, such as Classes, Tables, and Forms. Some elements are grouped into subcategories to provide a better structure. For example, Tables, Maps, Views, and Extended Data Types reside under Data Dictionary, and all Web-related elements are found under Web.

 Application Object Tree

You can navigate the AOT by using the arrow keys on the keyboard. Pressing the Right arrow key expands a node if it has any children.

Elements are ordered alphabetically. Because thousands of elements exist, understanding the naming conventions and adhering to them is important to effectively using the AOT.