Hi All,
we are upgrading an AX 2012 R3 TO D365FFO, but we need first to merge all our code in usr layer since it is one several layers and models , what is the best practice to do so ? and would it affect the data upgrade ?
Thank you,
Hi All,
we are upgrading an AX 2012 R3 TO D365FFO, but we need first to merge all our code in usr layer since it is one several layers and models , what is the best practice to do so ? and would it affect the data upgrade ?
Thank you,
thank you, so i shall create a project using the filter option of each model and export it, then import all models in other layers to usr layer.
You can't export/import a layer. And if you export a model, you can't import it to a different layer. Only with xpo you can import it to a different layer.
Thank you Nikolaos,
i will do it on separate new development machine, just to facilitate the code upgrade purposes, so i export usr layer, then export var layer, delete var, then delete usr , then import var to usr then import on top of it the usr layer right ? i know it is risky and it might have some minor issues.
Regards,
The layer of the code (or metadata, such as tables) doesn't impact data upgrade.
But what you just described will break your data in AX2012. All table and field ids would change and your system would not work anymore.
I'm not sure if/why you would need to move all code to usr. But if you need to do it, the process must be different.
I think that it should work if you just login to usr, export objects as xpo, then import them back. Now all objects should exist in usr.
Then you can delete the model from the lower layer. However there might be some issues so I can't guarantee that it will work.
Thank you Nikolaos, so i can export all elements from VAR then delete them, and import them to USR layer then do the code upgrade on LCS right ? then will do dataupgrade since all the tables will have same name in D365FFO right ?
Hi Mohammed,
How many layers do you have your customizations in?
I am not sure how you would merge into a single layer especially if you have created tables in these different layers (Table Ids would have been generated accordingly).
I would suggest having a single model per layer you have modified. This way you could lock these models after code upgrade (in D365) and only continue with a single model for future customizations.
The layer(s) of your code have no impact in data upgrade.
André Arnaud de Cal...
293,274
Super User 2025 Season 1
Martin Dráb
231,939
Most Valuable Professional
nmaenpaa
101,156
Moderator