Move customization after code upgrade

(0) Share

Report

Posted on by Hariharans87

Hi,

We are in the D365 upgrade phase and Its taking long time. In the middle, we are doing some customization on AX 2012 and tracking our changes on version control.

What is the best practice to move only our new customization to D365? Do we need to do the same customization from scratch? or Is there any tool or easy way to move?
Our new customization affecting more objects like forms, classes, table, enums, edt. Can we do the live data upgrade parallel once we move only data dictionary changes?

Thanks,

Hari

I have the same question (0)

All responses (1)

Answers (1)

Verified answer

JJ_Yadav on at

Like (0)

Report

Hi Hari,

In Ideal scenarios, best practice is to have code freeze in AX 2012 while upgrading the code and do minimal changes that affect current production environment. There is no tooling support to merge the incremental customizations back to D365 code base. However sometime its hard to avoid and delay changes in AX 2012 while code upgrade is happening in D365. One of the practice I have seen customer doing is parallel development - essentially in this approach while doing the changes in AX 2012 customer makes required changes in D365 environment as well. If there are lots of new object changes/added in AX 2012 then other option could be to upgrade the latest code using LCS and then manually extract the check-in the changes in D365. However upgrading the code again can be counter productive if the changes are small and it may be better to copy and paste.

Running test data upgrade with upgraded data dictionary code is one of the practice many customer do to exercise the test data upgrade. You can certainly do migrate data dictionaly elements first and make it compile error free and run the test data upgrade.

Was this reply helpful? Yes No