- 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
Label files will have their own model, and are checked in and out using the label editor. You may notice that it assigns an odd-looking label ID, such as @$AA101. This is a temporary label ID that will be used until the label is checked in, at which time it works out the next label ID.
This is usually seamless but you may notice odd labels might start to appear, like this:
Label @$AA101 is replaced by @BCL101
The problem makes sense when we understand what happens when labels are checked in. The label check-in process is as follows:
- Replace the temporary label ID with next global label ID from TFS.
- Replace all instances of the temporary label with the new global label ID.
- If the target element is not checked out, change the text of the temporary label to assist the developer in manually assigning the correct global label ID.
So, don't check in the objects before the labels are checked in, otherwise you will need to check each label and correct it.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.