Several months ago, I completed an upgrade from AX2009 to AX2012 R2 CU7. Both code and data were upgraded and the system will fully synchronize and compile. We did not go live with the project. We are now beginning an upgrade project to take us from AX2009 to AX2012 R3. What strategy can I use to take advantage of the upgraded customizations that exist in my AX2012 R2 version model store? My tentative plan is to do an in place upgrade from R2 to R3, export the code, the models and the model store, and then start with a fresh AX2009 to AX2012 R3 upgrade. Once I get to the code upgrade section I need to find the best way to bring in my previous work. I have some ideas, but I would like to hear suggestions from the community.
Thanks!
Lisa J
*This post is locked for comments
Hi,
I am doing the same thing, Upgrade AX 2009 to AX 2012 r3. Can anybody help me out what tentative downtime should i consider for this Source to Target method?
another one is what about in-built form customization transfer from AX9 to AX12? How can we accommodate that?
Need a help.Thanks in advance.
lispyj,
I read in Upgrade guide that you need to transfer your customized module offline on target system.
Hi Lisa
Now you are handling the upgrade to R3, so the version of the model file will be 6.2.x.x
I'm not sure, but if you were to try import this model file using a newer version of Management Utilities you will get an error.
If so, take a look at yetanotherdynamicsaxblog.blogspot.it/.../axutillib-ax-management-utilities.html
If works, you have to manage the porting of the custom code to R3.
Otherwise, you have to move the custom code using XPO from R2 to R3 and manage the porting.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156