Selecting the appropriate layer for our solution
by Mat Fergusson, Simon Buxton
Mastering Microsoft Dynamics AX 2012 R3 Programming
- Mastering Microsoft Dynamics AX 2012 R3 Programming
- Table of Contents
- Mastering Microsoft Dynamics AX 2012 R3 Programming
- Credits
- About the Authors
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Preparing Our Solution
- The technical architecture of a solution
- Minimizing the footprint of changes
- Selecting the appropriate layer for our solution
- Configuring source control
- Creating the models
- Creating a label file
- Creating a project
- Setting up the default project and model
- Designing the technical solution
- Designing test plans
- Summary
- 2. Creating Data Structures
- 3. Creating the User Interface
- 4. Creating Business Logic and Hooking into Core AX
- Moving table validation and logic into a class
- Adding navigation
- Number sequences
- Hooking into standard AX logic using event handling
- Summary
- 5. Adding Business Intelligence
- 6. Extending the Solution
- Adding secondary list pages
- Using menu items to change the vehicle status
- Adding a drop dialog to change vehicle group
- Exposing the vehicle group logic as a custom web service
- Summary
- 7. Designing Your Security Model
- 8. Customizing Standard AX
- Key goals when customizing standard or third-party code
- How to determine where to make the change
- Adding fields to tables
- Integrating a custom module with standard AX
- Using an extension table for additional fields
- Changing the behavior of a class
- Extending a framework – vendor electronic payments
- Summary
- 9. Advanced Features and Frameworks
- Adding custom filters to list pages
- Advanced methods of adding ranges to list pages
- Using the SysOperation framework
- Using the SysOperation framework execution modes
- Customizing the user interface displayed by the SysOperation framework
- Tracking progress of scheduled tasks
- Understanding the global address book
- Accessing the financial dimension framework
- Summary
- 10. Advanced Development Techniques
- 11. Unit and Performance Testing
- A. Efficient Design and Development with Microsoft Dynamics AX
- B. Using Version Control
- C. Code Editor Scripts
- Index
This choice of layer is normally straightforward. As an ISV, we will use the ISV layer; as a VAR, the VAR layer; and so on.
We can sometimes choose, as the end user between the higher layers, CUS and USR. It does not normally matter which, as long as we stick to it. Incorporating more layers adds to the maintenance cost.
The main reason for using both CUS and USR is when we (as an end user organization) have multiple installations of AX that share a common base application. We would manage the CUS layer centrally, and each installation will be responsible for their installation-specific customizations in the USR layer.
The layer is selected in the AX Configuration Utility. To change the current layer, follow these steps:
- Open Microsoft Dynamics AX 2012 Configuration Utility. This is accessed from the Administrative Tools Windows program group.
- Select the desired configuration from the Configuration drop-down list and select the Developer tab.
- Select the appropriate layer from the Application object layer to open drop-down list.
- If the layer is not
usr, you will need to enter the development license code in the field Development license code, and again in Confirm license code. - Press OK.
When we open the AX client the next time, the configured layer will be used.
-
No Comment