Notifications
Announcements
No record found.
Is it possible to take project backup from 7.2 and import into 10.0.9 version to push the delta code, instead of re-running code upgrade tool?
I think you need to run code upgrade tool to make your "pre-8.0" code compatible with "post-8.0" D365.
Also, you should not store / move your code as Visual Studio projects! Instead you can try to deploy a 10.0.9 dev VM and get latest from source control and see if you get some errors.
Anyway you need to build a new package to deploy code to test/prod.
Here is also MS documentation about the topic: docs.microsoft.com/.../upgrade-latest-update
Upgrade – The process of moving from one official release of Finance and Operations to the next release, for source environments prior to version 8.0. Some examples are the move from 7.1 to 7.3, or from 7.3 to 10.0.1. The process involves setup of a free sandbox environment, code upgrade, and data upgrade.
Thanks Nikolaos. I can understand that we need to re-run upgrade tool for delta code if we are not freexing the code. My another query is, if i run the code upgrade tool for first time and if i check in any changes to the release branch created as part of code upgrade tool, will it get override when i re-run the code upgrade tool for my delta code? We want to run both BAU as well as code upgrade parallely wtihout code freeze. Please suggest.
I'm not sure if I understand what you mean by "delta code" and "BAU".
Every code upgrade creates a new folder in the Releases, so if you run code upgrade two times, you will get two folders. Nothing gets overwritten, but also if you made some manual changes to the first Release folder, they will not be carried over when you do a new code upgrade.
I strongly recommend a code freeze, doing only critical fixes while you upgrade your 7.2 code to the v10 world. All these fixes must be migrated manually from your support branch to your new upgraded codebase.
The brunt of your work will be to get rid of over-layering and implement extensions instead. Code upgrade does very little with regard to extensions. So there is very little use in rerunning the code upgrade because likely there's no good way to merge the code anyway (unless your 7.2 is already overlayering free, but in that case code upgrade isn't that useful anyway).
Long story short. You're likely just going to have to copy/paste (/reimplement) any changes you're doing in 7.2 into your upgraded 10.0.9 code base anyway. If you're having to move tons of code from overlayering to extensions, then even more you will likely just have to copy/paste or manually merge code anyway.
Thanks Joris. That is what i want to understand as our code is mostly on extension, do we really need to use code upgrade tool second time if i implement any change in 7.2 after running code upgrade tool first time? or just a project export from 7.2 and import into 10.09 will work assuming delta components are all new extension components?
Well, look at the first upgrade you did. I'm guessing the code upgrade didn't change much in your code at all? The code upgrade largely just merges code between layers, so with extensions I would expect not much was done. If that is indeed the case, I think you'll agree you can just move the code. I would NOT do project export. If I had my way I would rip that feature out, but sadly I'm not allowed to :-)
Assuming you use source control, can't you just merge your change from your 7.2 branch into the 10.x branch?
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 592 Most Valuable Professional
André Arnaud de Cal... 478 Super User 2025 Season 2
BillurSamdancioglu 305 Most Valuable Professional
