Exploring the Application Object Tree (AOT) in D365 Development Platform

 


The Application Object Tree (AOT) is a key element in Microsoft Dynamics 365 (D365) development, acting as a core for customisation and extension. It is essential that developers know the elements in AOT and everything in D365 application has related object in AOT, these AOT elements then convert into dll to make the complete D365 FinOps application running. 



What is AOT?

 

Within the D365 development environment, there is a structural collection called the Application Object Tree (AOT). It acts as a repository for classifying, maintaining, and arranging different application components, such as forms, data types, tables, and reports. The Dynamics 365 application can be designed, modified, and expanded by developers using AOT.


Classification of AOT

 

AOT is classified into two views Model view and classic view. Now let's examine the differences between Model View and Classic View in the Dynamics 365 development platform's Application Object Tree (AOT).

You can switch from the classic view to the model view from AOT.

By right click on AOT and select model view.

Model View


In model view. Each model is listed separately in this view. As in the classic view, each model's elements are grouped. The model view is shown in below picture. You'll see that the Fleet Management model's node has expanded and that the model's components are grouped just how they would be in the classic view.




Classic View

On the other side, the Classic View is the standard arrangement of the AOT's elements without the use of models. This view removes the extra layer of model-based organization and arranges the elements in a flat structure.


Elements in AOT


With AOT, elements are arranged in a tree-like structure that makes it easy for developers to move between layers and categories. A few important elements are as follows:


Data Types: Contains metadata about extended data types and Enums.


Data model: Contains metadata about tables, Views, Entities, and Queries.


Code: Contains metadata about the code which use to run different process.


User Interface: Represent the user interface components of the application, like forms, tiles, menu and menu items.

Analytics:  Encompasses several key components designed to provide business intelligence and insights.

Reports: Contain Report designs and resources used in reports like pictures.

Business process and workflow: Contains the workflow model elements used to create a workflow configuration. This node contains Categories, Tasks, Approvals, and Templates.

Label Files: Contain Label text for different languages, you can define label in almost all major language.

Resources: Used to store various types of files that can be utilized within the application. These files can include XML, Json, text file 

Configurations: This contains license code and configuration keys, these configurations help developer to configure application to meet specific business needs and ensure that only the necessary features are available to users.

Security: Contains security elements like  Privileges, duties and roles.

References: Contain references for different external resources like dll.

Services: Contain service related objects like service and service group which help developer to develop different integration scenarios. 

System documentation: This node have refers to documentation and configuration settings that are essential for system management and administration.



Comments

Post a Comment

Popular posts from this blog

Setting Up Project for D365 Finance And Operation

Image
  To develop the Microsoft Dynamics 365    Finance and Operation application, you need a development environment. In this article, you will learn how to create project in VS for D365 development. Before going into  deep, If you don't have a development vm, follow the steps to access free vm  how to configure a free VM for D365 F/O . Setting Up Project For Dynamics 365  Whenever a developer needs to add functionality in Microsoft Dynamics 365 For finance and operation, the first step is to create the project. Now, Let's discuss how to create a project for D365 in Visual Studio. Prerequisites Visual Studio IDE Before diving into the setup, ensure that you have Visual Studio IDE installed. Run Visual Studio as an  administrator  to avoid potential errors during project building. Checking Dynamics 365 Extension Make sure Visual Studio has the Dynamics 365 extension. Navigate to the  Extensions tab , and if the  Dynamics365  extension is...
Read more

Package, Model, and Projects in D365 FinOps

Image
To excel in D365 FinOps development, developers must thoroughly understand four key terminologies: Package, Model, Project, and Element. Customization in D365 primarily revolves around Elements. For a comprehensive understanding of all elements, you can review Exploring the Application Object Tree (AOT) in the D365 Development Platform.   Knowledge of Package, Model, and Project is essential for customizing an element. Package A Package is a compilable and deployable unit that contains one or more models.It includes model metadata, binaries, and other associated resources. Packages are essential for deploying customizations and solutions within the Dynamics 365 environment. Model. A Model is a design-time concept. which contain elements and references to other models. These elements typically constitute a software solution and can include customizations of an existing solution. This help organize and manage the development and customization of various functionalities within D365 Fi...
Read more