Patch Layers

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Each layer in Microsoft Dynamics AX has a corresponding patch layer that can be used to incorporate updates to your application or to store conflicts when you import models into a layer. The following table shows the layers along with the corresponding patch layers:

Providing Updates

The patch layers are designed to make it easy to incorporate updates in your application. The basic idea is that when a minor update or correction is made, it is distributed in a patch file. Modified objects in the patch file are automatically used because they take precedence over the regular application objects.

Storing Conflicts

By default, each layer contains a model that corresponds to the name of the layer. You can add additional models to layers that you have access to, depending on your license configuration. You can have different versions of the same element in models that are in different layers, but each element within any one layer must be unique.

If the same element exists in two models, and you try to import both models into the same layer, the element that exists in both models will cause a conflict. To mitigate the conflict, you can choose one of three options:

• Abort the operation and leave the model store unchanged.

• Overwrite existing definitions with the definitions in the new model.

• Create a new model in the patch layer that contains the conflicts.

If you choose the third option, a conflict model is created in the patch layer that corresponds to the layer you are importing the model into. The conflicting elements are moved to this model. You can then decide how to resolve the conflicts. For more information about conflict models in a patch layer, see How to: Resolve Conflicts After Importing a Model.

See also

Layers

Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.