RSS Feed (xml)
Dynamics AX 2009 consists of sixteen application object layers that contain all the elements you see in the AOT. These layers can be looked at as an onion with multiple layers. In the middle is the core application in the SYS layer and the outermost layer is the user layer USR. Therefore, when any application element is being executed the system will look at the outermost code layer first to see if there is any code for that element; if not, it peels a layer off the onion, and tries the next layer. When it hits a layer where the element exists, it will use the code from this layer, and will not continue to peel off layers to find code for that element in the innermost layers.
As you might have noticed, the above figure only shows half of the layers. Each of the layers in the illustration, except the HFX, SL1, SL2, and SL3, has a patch-layer. The patch-layers are used for service-packs and hotfixes, and exist one layer outside its corresponding main layer. If we look at the SYS layer there is actually a SYP layer between the SYS layer and the GLS layer.
The HFX, SL1, SL2, and SL3 layers are new in Dynamics AX from version 2009, but can be found in previous versions as DIS, DIP, LOS, and LOP. The list below is taken from the Dynamics AX 2009 SDK and provides an explanation of each layer:
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 the modified version of the form is used.
HFX HFX is an application object patch layer reserved by Microsoft for futurepatching or other updates.
SL1, SL2,or SL3 A layer where the distributor can implement vertical partner solutions. SL is an abbreviation for SoLution.
BUS When a business partner creates their own generic solution, their modifications are saved in the BUS layer and the top-level application objects are used.
VAR Value Added Resellers (VAR) 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, such as in their reports. These modifications are saved in the USR layer.
Each of these layers is represented in the application folder with a .aod file if there is any code in the solution in the layer. The same goes for the patch layers. This means that the application object file for the SYS layer is AxSYS.aod, and as the patch layer for SYS is called SYP, the patch file would be AxSYP.aod.
As you might have noticed, the above figure only shows half of the layers. Each of the layers in the illustration, except the HFX, SL1, SL2, and SL3, has a patch-layer. The patch-layers are used for service-packs and hotfixes, and exist one layer outside its corresponding main layer. If we look at the SYS layer there is actually a SYP layer between the SYS layer and the GLS layer.
The HFX, SL1, SL2, and SL3 layers are new in Dynamics AX from version 2009, but can be found in previous versions as DIS, DIP, LOS, and LOP. The list below is taken from the Dynamics AX 2009 SDK and provides an explanation of each layer:
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 the modified version of the form is used.
HFX HFX is an application object patch layer reserved by Microsoft for futurepatching or other updates.
SL1, SL2,or SL3 A layer where the distributor can implement vertical partner solutions. SL is an abbreviation for SoLution.
BUS When a business partner creates their own generic solution, their modifications are saved in the BUS layer and the top-level application objects are used.
VAR Value Added Resellers (VAR) 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, such as in their reports. These modifications are saved in the USR layer.
Each of these layers is represented in the application folder with a .aod file if there is any code in the solution in the layer. The same goes for the patch layers. This means that the application object file for the SYS layer is AxSYS.aod, and as the patch layer for SYS is called SYP, the patch file would be AxSYP.aod.
No comments:
Post a Comment