Application Object Layers

Application object layers hold everything in the Application Object Tree (AOT).

The layers are a hierarchy of levels in the application source code to ensure that you can make modifications and additions without interfering with the application objects on the level below your own. When you make an object modification on one level, the modification overshadows the object on a lower level. You could for example choose to add e-mail information to a standard form. The addition would be saved on your level only; the revised form would replace the standard form, but you would always be able to go back to the original one on the level below your own simply by removing the new form.

Three customer groups have an interest in adding and modifying application objects:

  • Application developers who create the standard application

  • Business partners

  • End users of Microsoft Dynamics AX

Each of these three groups has two layers in which they can add and modify.

SYS

The standard application is implemented at the lowest level, the SYS layer.

The application objects in the standard application can never be deleted.

GLS

When the application is modified to match country/region specific legal demands, these modifications are saved in a separate layer, the GLS layer. If an application object, for example a form, is modified in the GLS layer the modifications are saved in the GLS layer only and Microsoft Dynamics AX ensures that the modified version of the forms is used.

DIS

When the application is modified to match country/region specific legal demands, these modifications are saved in a separate layer, the DIS layer (for DIStributor). If an application object, for example a form, is modified in the DIS layer the modifications are saved in the DIS layer only and Microsoft Dynamics AX ensures that the modified version of the forms is used.

LOS

A layer where the distributor can implement local partner solutions. LOS is short for LOcal Solution.

BUS

When a business partner creates their own generic solution, their modifications are saved in the BUS layer and Microsoft Dynamics AX ensures that the top level application objects are used.

VAR

Value Added Resellers can make modifications or new developments to the VAR layer as specified by the customers or as a strategy of creating an industry specific solution. Such modifications are saved in the VAR layer.

CUS

The supervisor or administrator of an end-user installation might want to make modifications that are generic to the company. Such modifications are saved in the CUS (CUStomer) layer.

USR

End users might want to make their own modifications, for example their own reports. Their modifications are saved in the USR layer.

Each layer is saved in a separate file called Ax<layer>.aod, for example Axsys.aod for the SYS layer, Axdis.aod for the DIS layer and so on. The .aod extension is an acronym for Application Object Data file.

In addition to the six layers, each layer has a patch layer.

For each layer, there is a corresponding label file.

Community Additions

ADD
Show: