Data and Engine Class Design Pattern [AX 2012]
Updated: April 30, 2014
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
Use this pattern for the following situations:
-
When data can be manipulated by programs and data can be different from situation to situation.
-
When manipulation can be different from situation to situation.
One class hierarchy defines the different data structures, and another class hierarchy defines the different manipulations. As a user of the class hierarchies, you always use and call methods on the superclasses.
The objects are the data (hierarchies). The methods on the objects are implemented by using the manipulation hierarchies.
 Note |
|---|
|
Be sure to separate data and functions correctly. |
The following illustrates an example of the data and engine class design pattern.
Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.