mmm you should do code upgrade and a test data upgrade and then when this is all okay then you just do a data upgrade when the customer is ready to switch over We have a case of having done code and test data upgrade and now the customer is taking a good 6 months to test everything (are are doing some changes in AOT during this time also so we are having to update both 3.0 and 2009 ...no problem so long as you factor in effort for 2 data upgrades in your cost (FYI it took us about 40 hours to get the first data upgrade to work and completed for an Ax3.0 SP2)
_____ From: Axapta-Knowledge-Village@yahoogroups.com [mailto:axapta-knowledge-vill...@yahoogroups.com] On Behalf Of nanukuttan rinish Sent: 27 April 2009 15:51 To: Axapta Subject: [Axapta-Knowledge-Village] need help in upgrade Hi all, I have a doubt during the upgrade, please considered a scenario where we are taking an upgrade project from client "xyz" to upgrade from Ax3.0 to Ax2009. Say if we are taking the client's Ax3.0 environment and database and we are successfully upgrading it. We will imagine that the upgrade takes 2 months to complete.In the meanwhile the customer would have made lot of transaction in his Ax3.0 environment. Now how do we update the records which are added in the 2 months period in Ax2009 environment. Regards Rinish.N _____ Explore your hobbies and interests. Click <http://in.rd.yahoo.com/tagline_groups_6/*http://in.promos.yahoo.com/groups/ > here to begin.
