Best Practices: Relative Upgrade Costs
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
The following table provides an overview of the relative upgrade cost for a change to an existing application object.
The upgrade cost is not an absolute value. This table is meant to give only an approximation of the work involved.
Application Object Type |
Cost if functionality added |
Cost if functionality changed |
|---|---|---|
Form |
High |
High |
Report[1] |
High |
High |
Report Template |
Low |
Low |
Query |
Medium |
Medium |
Menu |
Medium |
Medium |
Table collection |
Medium |
Medium |
Table |
Low |
Medium |
Class |
Low |
Medium |
Extended data Type |
Medium |
Medium |
Base Enum |
Medium |
Medium |
Menu Items |
Medium |
Medium |
[1] Modifications to a report can be done by adding a new design. In this case, the upgrade cost is considered Medium.
If new functionality is added to a Microsoft Dynamics AX application as new stand-alone application objects, the cost of upgrading is likely to be much lower than if the functionality was created by modifying existing objects.
See also
Best Practice Design Guidelines for Cost-Efficient Upgrades
Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.