- #MORPHX AND THE APPLICATION OBJECT TREE HOW TO#
- #MORPHX AND THE APPLICATION OBJECT TREE UPDATE#
- #MORPHX AND THE APPLICATION OBJECT TREE VERIFICATION#
- #MORPHX AND THE APPLICATION OBJECT TREE CODE#
How to: Import Application Objects by Using the AOT
#MORPHX AND THE APPLICATION OBJECT TREE HOW TO#
This section describes the AOT and its contents, how to use the AOT to define application objects, and how to import and export definitions of application objects.įor reference information about the properties for element nodes in the AOT, see Properties of AOT Elements. The AOT also contains application resources, references, and documentation. In Microsoft Dynamics AX, application objects are defined in the Application Object Tree (AOT) and are instantiated at runtime. If the option isn’t available, either the element isn’t used or the cross-reference hasn’t been updated.įigure 2-31 shows where the prompt method is used on the RunBaseBatch class.Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012 To access usage information, right-click any element in the AOT and point to Add-Ins > Cross-Reference > Used By. Here is an example: // Prints ID of M圜lass, such as 50001įor more information about intrinsic functions, see Chapter 20, “Reflection.”
#MORPHX AND THE APPLICATION OBJECT TREE VERIFICATION#
Using intrinsic functions provides two benefits: you have compile-time verification that the element you reference actually exists, and the reference is picked up by the Cross-Reference tool. The intrinsic functions are named Str or Num, respectively. An intrinsic function can evaluate to either an element name or an ID. It’s a good idea to use intrinsic functions when referring to elements in X++ code.
![morphx and the application object tree morphx and the application object tree](http://datacenter.github.io/acitoolkit/docsbuild/html/_images/apptopo.png)
#MORPHX AND THE APPLICATION OBJECT TREE CODE#
When the Cross-Reference tool is updating, it scans all metadata and X++ code for references to elements of the kinds listed in the xRefKind subnode. You can find a complete list of cross-referenced elements by opening the AOT, expanding the S ystem Documentation node, and clicking Enums and then xRefKind. The information that the Cross-Reference tool collects is quite comprehensive. Type hierarchy Stores information about class and data type inheritance.įor more information about these subsystems and the tools that rely on them, see the AX 2012 SDK ( ).It is primarily used by the query form and the Reverse Engineering tool. Data model Stores information about relationships between tables.In addition to the main cross-reference information, two smaller cross-reference subsystems exist: To do so, right-click the project and point to Add-Ins > Cross-Reference > Update.
#MORPHX AND THE APPLICATION OBJECT TREE UPDATE#
Another option is to update cross-references manually for the elements in a project. This option slows down compilation, however. If you work in a local development environment, you can keep the Cross-Reference tool up to date by enabling cross-referencing when compiling. Updating the Cross-Reference tool nightly is a good approach for a shared environment. If you work in a shared development environment, you share cross-reference information with your team members. Keeping the Cross-Reference tool up to date is important if you want its information to be reliable. Updating the Cross-Reference tool also compiles the entire AOT because the compiler emits cross-reference information. To update the Cross-Reference tool, on the Tools menu, point to > Cross-Reference > Periodic > Update. The footprint in a database is about 1.5 gigabytes (GB) for a standard application. The update typically takes several hours. You must update the Cross-Reference tool regularly to ensure accuracy. If you’re changing an element, you need to know which other elements are affected by your change.
![morphx and the application object tree morphx and the application object tree](https://analytics.infozone.pro/wp-content/uploads/2018/11/Statistical_Inventory_Control_SIC_4.png)
If the product documentation doesn’t help, you can use the Cross-Reference tool to find real implementation examples. Here are a couple of typical scenarios for using the Cross-Reference tool: AX 2012 provides the Cross-Reference tool for accessing and managing cross-reference information. With cross-references, you can determine which elements a particular element uses and which elements other elements are using. If an element uses another element, the reference is recorded. The concept of cross-references in AX 2012 is simple.