|
|
| |
|
Top Ten Tips for a successful upgrade to Dynamics AX 2009 |
|
| |
1. |
Business Process Documentation: Document your customization with the business functionality that they provide. Determine if there is any overlap between customizations you have created and new functionality in Dynamics AX 2009. |
|
|
|
|
2. |
Code Compare: Use the Dynamics AX Code Compare tool to identify code conflicts. The code compare tool will not only show changes between two versions of an element as it did before but also Include information about the original (3-way compare) and provides better handling of renamed nodes. |
|
|
|
|
3. |
Upgrade Project: Create an upgrade project so you can identify what code you are porting over versus which code you will be deleting due to overlapping conflicts. If there is significant overlap in functionality, re-implement one version (yours or Microsoft). If possible choose the Microsoft version to stay closer to the standard |
|
|
|
|
4. |
Layered Code: If you haven’t already, take this opportunity to layer your customization in appropriate layers |
|
|
|
|
5. |
Layered Upgrade: Upgrade one layer at a time. Use Show All Layers |
|
 |
Read an independent analysis by Ignify on what is new in Microsoft Dynamics AX 2009, rating of each new feature on a scale of 1-10 and an unbiased opinion of how useful and how complete the feature is with any recommended future enhancements.
|
|
| Length: 174 pages |
|
| Format: PDF |
|
| Click here to download the paper |
|
|
|
|
|
|
|
|
| |
6. |
Test Environment: Verify a successful upgrade on a test environment. Test for functionality, reports and performance |
|
|
|
|
7. |
Training: Train your user team on the new functionality so they can be part of your testing team and are able to leverage the new functionality that AX 2009 brings to your organization |
|
|
|
|
8. |
Server Environment: If possible do an in-place on a the same environment instead of migrating servers. This reduces the complexity of the upgrade. That is not to say that you cannot migrate to a new environment. Factor in additional time /complexity for that approach if you need to go down that path |
|
|
|
|
9. |
Unit and Regression Testing: Ensure you at least have test plans written that reflect your business processes. If you have a high degree of complexity automate your unit testing using the unit test framework. |
|
|
|
|
10. |
Source Control: Dynamics AX 2009 offers a great source control framework. Take this opportunity to bring in your code into the source control framework. |
|
And one more tip that is obvious but you need to ensure you don’t forget to do it. Backup BEFORE you upgrade. If you have questions email us at DAXUpgrade@ignify.com |
|
|
 |
|
 |
|
 |
|
| March 12, 2010: |
| 11.00 am Pacific: Ignify eCommerce with Microsoft Dynamics ERP and Sage ERP demonstration. Click here to register |
|
|
|
| April 24-27, 2010: |
| Visit Ignify at Booth #501 Microsoft Dynamics Convergence 2010, Atlanta GA. View Agenda and Register |
|
|
|
| June 15-16, 2010: |
Ignify will show case Microsoft CRM for call centers. ACCE - Global Gathering for the Contact Centers, Booth #28 in Sheraton Hotel,
New Orleans LA |
|
|
|
| Feb 24, 2010: |
| Saflok (A member of the Kaba Group) – A leader in access control solutions servicing hospitality segments servicing to the vacation rental market, multihousing market, commercial, military and government facilities is live on Ignify eCommerce |
|
|
|
| Feb 10, 2010: |
Port of Long Beach Selects Ignify and Microsoft Dynamics AX ERP to Drive Customer Service and Operating Efficiencies.
More info |
|
|
|
|
