AX 2012 Development – Layering in AX and Why We Have Code Conflicts

by | Updated August 15, 2016 | Development, Dynamics AX

The Layer concept is unique to Microsoft Dynamics AX Development and can cause some confusion for developers who are new to the AX development environment. In Dynamics AX we have 8 standard layers, plus 8 patch layers. The layers are fully described and documented elsewhere, so this article will not rehash that information. However, it is helpful to keep in mind the order of layers from highest to lowest, described here.

The important thing to understand is that when an object/element is modified, some or all of that element is copied from a lower level (the next highest layer where it exists) to the current layer. Note: For classes and tables, only the modified field or method is copied to the current layer.

AX will always use the version of the element on the highest (outermost) layer.

To illustrate, let us assume the current layer is cus and we added a new method and modified an existing method on class CustVendCheque.

New method “some_method()”

Some Method

 

Modified method checkDateOk

Classes CustVendCheque

 

We can easily take a look at only the cus layer changes by exporting the Application Object Layer.

Application Object Layer

The xpo file will contain only the method we modified and the new one created, since those are the cus layer changes. (Note: Code lines replaced with … below for brevity)

Taking this example one step further, let us look at what might happen if someone makes a change to the checkDateOk method on the var layer. Assume that this developer was working in another environment where your cus layer changes do not exist.

He adds the following code…

Remember, this class existed on the syp layer initially, so you and the other developer pulled the same version of the class to make your changes but on different layers. Because cus is the higher layer, those changes will “overlayer” the var layer changes unless you do something to intervene. This is a code conflict, and a decision must be made about what code to keep.

Comparison in Dynamics AX

 

The above code is oversimplified, of course, but this is exactly what happens when you install a CU or hotfix. Changes in the syp (patch) layer may be overlayered by customizations of those same elements in higher layers.

 

Related Posts

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Upcoming Events

august

05aug10:00 am10:30 amOn the Job with Dynamics 365 - Manufacturing Shipping / Receiving Department

05aug12:00 pm1:00 pmHow Ag Coops Can Simplify Processing Equity Payments using Levridge

12aug10:00 am10:30 amWhy Levridge Grain? How to Achieve Efficient and Accurate Scale Tickets

12aug12:00 pm1:00 pmThe Three Paths to Dynamics 365 Finance and Supply Chain from Dynamics AX

13aug11:00 am12:00 pmConfab with Stoneridge - Livestream - Inspire Keynote Breakdown

19aug10:00 am11:00 amWhat is Levridge? An Overview of the Ultimate Ag Solution

19aug12:00 pm12:30 pmThe Modern Manufacturer - Death by Safety Stock

27aug11:00 am12:00 pmConfab with Stoneridge - Livestream - Dynamics 365 2020 Wave 2 Preview

september

02sep10:00 am10:30 amThe Modern Manufacturer - Cycle Count Management

09sep11:00 am12:00 pmModernizing Batch Manufacturing - Ensuring Compliance and Quality Control

16sep10:00 am10:30 amThe Modern Manufacturer - Product Lifecycle Management

30sep10:00 am10:30 amThe Modern Manufacturer - Return Management

About Stoneridge
Stoneridge Software is a unique Microsoft Gold Partner, with emphasis on partner. With specialties in Microsoft Dynamics 365, Microsoft Dynamics AX, Microsoft Dynamics NAV, Microsoft Dynamics GP and Microsoft Dynamics CRM, we focus on attracting the most knowledgeable experts in the field to our team, and prioritize delivering stellar solutions with maximum impact for your business. At Stoneridge, we are deeply committed to your results. Each engagement is met with a dedicated team, ready to provide thorough, tailored, and expert service. Based in Minnesota, we intentionally “step into your shoes,” wherever you are. We focus on what you care about, and develop trusting, long-term relationships with our clients.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!

X