After you open a new AOT window, you can drag elements into the nodes, saving time and effort when you’re developing an application. This action was used to create the screen capture of the AccountingDistribution element shown earlier in Figure 2-4. It opens a new AOT window with the current node as the root.
#Morphx and the application object tree manual#
To perform manual resolution, follow these steps: Typically, the general integrity of what’s shown in the AOT is managed automatically, but some operations, such as restoring the application database or reinstalling the application, can lead to inconsistencies that require manual resolution to ensure that the latest elements are used. This action refreshes both the on-disk and the in-memory versions of the element. You do this by right-clicking the element, and then clicking Restore. This autorefresh functionality eventually updates all changes, but you might want to force the refresh of an element explicitly. To ensure that the local versions of remotely changed elements are updated, an autorefresh thread runs in the background.
If several developers modify elements simultaneously in the same installation of AX 2012, each developer’s local elements might not be synchronized with the latest version. You specify the frequency of autosave in the Options form, which is accessible from the Tools menu. When the developer explicitly invokes the Save or Save All action.Sales and marketing management, also called customer relationship management (CRM)Īpplication frameworks and development toolsįIGURE 2-4 A dirty element in the AOT, indicated by a vertical line next to the top-level node, AccountingDistribution.Ī dirty element is saved in the following situations: Table 2-2 contains a list of the most common prefixes and their descriptions. For example, if a company called M圜orp is building a payroll system, it could use the prefix McPR on all elements added. Consider using a prefix that identifies the company and the solution. This additional prefix will help prevent name conflicts if your solution is combined with work from other sources. When building add-on functionality, in addition to following this naming convention, you should add another prefix that uniquely identifies the solution. The name CustPaymReconciliationImport describes a similar functional area and action for the Customer business area. For example, in the name VendPaymReconciliationImport, the prefix Vend is an abbreviation of the business area name (Vendor), PaymReconciliation describes the functional area (payment reconciliation), and Import lists the action performed (import). Prefixes are commonly used to indicate the team responsible for an element. The business area name is also often referred to as the prefix. With this naming convention, similar elements are placed next to each other. Because there are thousands of elements, it’s important to understand the naming conventions and adhere to them to use the AOT effectively.Īll element names in the AOT use the following structure: Pressing the Right Arrow key expands a node if it has any children.Įlements are arranged alphabetically. You can navigate through the AOT by using the arrow keys on the keyboard.
0 kommentar(er)
