I am in the process of upgrading from AX 2009 to AX 2012. The application that I am working on dates all the way back to AX 3. I am currently performing the code upgrade.
This application has been very highly modified by a number of different developers over the years. Alot of these modifications are no longer relevant or necessary. One example is the Project table in AX 2009 that has over 30 custom fields where only 2 of them are actually being used.
My approach to upgrading to AX 2012 in this case is to only bring modifications accross to AX 2012 that are relevant. In other words I am trying to do a huge cleanup and not bring accross all the rubbish that I dont need. This means that I am not bringing the entire VAR layer accross to AX 2012, I am doing a re-implementation. I am using the cross referencing tool in AX 2009 to check where these fields are being used or not being used and I know the application modifications extremely well since I rebuilt all the functionality recently.
My question here is:
When I come to doing the data upgrade, am I going to have issues upgrading the data from the AX 2009 tables to the AX 2012 tables when there are custom fields in AX 2009 database that do not exist in the AX 2012 database? I am hoping that the data in these fields will simply be dropped from the database.
This might seem like an unusual question, but whilst I have done a few code upgrades, I have never actually had the opportunity to do the data upgrade, nor have I been faced with having to remove unwanted fields.
If someone could please advise on this subject it would be greatly appreciated.
Sarah
