Announcements
Hi,
We are upgrading from Ax2012 R3 CU8 to D365 FO.
Custom codes are available in VAR, CUS and USR layer. Single default model used in each layer for AX2012 customization s.
Please suggest best approach for code migration.
Do we need to bring all customization in single layer and model in AX2012 and then export model store to LCS ?
Is it fine to export existing model store with customization s in various layer and upload in LCS for upgrade ? In this case can we merge the different output models in D365 to one single model ? Will this reduce number of overlayering conflicts ?
Please note customer may not have AX2012 CUS & VAR layer licenses anymore with them. Not sure though.
Please suggest.
Best regards.
Hi Anudeep,
As mentioned in the documentation, it is recommended to first update to the latest available cumulative update. That is for both a data and code upgrade.
Hello Team,
Can you please provide the answer for the above question ?
Hello Andre,
We currently have AX 2012 R3 CU8 in our system and would like to upgrade to Dynamics 365 finance and Operations.
We only want to do code upgrade (via LCS) from AX 2012 R3 to Dynamics 365 and for data upgrade we would like to use the data migration path where only master data, and opening balances will be uploaded to Dynamics 365.
My question is - Can we directly do the code upgrade from AX 2012 R3 CU8 to Dynamics 365 F&O without first applying any KB fix on CU8 or without upgrading to CU13 ? or it is mandatory to upgrade to latest cumulative update CU13 (only for Code upgrade).
I saw the below link where it is mentioned - "Upgrade is currently only supported from either Dynamics AX 2012 R2 or Dynamics AX 2012 R3. For each release, please update to the latest available cumulative update before upgrading to latest finance and operations application release."
But we are not going to upgrade any data at all rather we are going to do the data migration.
docs.microsoft.com/.../data-upgrade-2012
Can you please help me to provide the answer ?
Hi Sayan,
Yes, you can create one large xpo file; do a fresh installation and then import it to a certain layer.
Thanks Martin for your suggestion.
As customer is not aware of if they have valid CUS & VAR layer licences with them anymore. Will it still be possible for me to merge all the 3 layers into USR layer?
For removing CUS & VAR layers I can do a fresh installation of Ax2012 and import USR layer then.
Hi Sayan,
If it will be considered to have one owner of the software who will maintain it, then it makes sense to merge them. Looking at your latest reply, I do agree with Martin to merge it already in AX2012.
Then merge layers already in AX 2012. You would make things much more complex for you if you upgraded all three layers and tried to merge them later in F&O.
Thanks Andre for your suggestion.
In my case there are plenty of custom objects which are created in VAR layer and then modified in CUS/USR layer in Ax2012.
My idea is to merge the objects so as to minimize effort of conflict resolution due to over-layering & refactoring to extensions.
Hi Sayan,
Usually, the layers are separated because of responsibilities. The VAR layer is intended for a partner add-on, the CUS is used for customer specific bespoke adjustments and the USR layer for some user specific changes.
If you want to merge it into one layer, then it might be possible to first use the code upgrade tool and then in Dynamics 365 merge them.
However you can also export the objects as xpo in AX2012; remove them in one layer and import back in another layer before the upgrade.
Thanks for your reply Ludwig.
The customization s are very specific to the organisation and not available in D365FO. So would like to bring all customization and data first and if required will remove few later.
Question here is which method is recommended considering that customization s are available in VAR, CUS and USR layer..
André Arnaud de Cal...
293,302
Super User 2025 Season 1
Martin Dráb
232,108
Most Valuable Professional
nmaenpaa
101,156
Moderator