You’re offline. This is a read only version of the page.
We want to migrate from ax 2012 6.0 to ax 2012 r3 6.3. Yes we did go though in-place upgrade guidelines but we have some questions.
1 if we export isv model from old version (6.0) and import it on new R3 6.3 will it work?
2 if we need to change code to make it work on R3 than how many classes do wee need change? means, how could we know that how many new elements added and removed by microsoft from base classes?
3 Do we have to do this manually or is there any tools that would show us changes needed to be done/fix to make OLD isv module work on R3?
Any help would be appreciated.
Thank You
Hi s14raj,
I'm sorry to read that you don't have support from your ISV. Did you terminate the contract or are they not active anymore? You can't import a model in another layer. So, try to see if you can solve the merge issues in the VAR or another layer.
Hi André,
We are in the condition right now where we don't have any help from our ISV vendor so we need to do this upgrade ourselves. Now problem is that we don't have a developer licence for ISV layer (We only have runtime licence for this layer).
We have a developer license for VAR layer. So can we move ISV layer code into VAR layer which will reside with VAR layer code? We don't much care about future updates. We just want to make it work for now.
When we import or install any module it goes directly into its respective layer. So how can we import or install ISV code into VAR layer? could you please guide on this?
Thanks.
Hi s14raj,
You got the answer on the first and third question from Mansour. It would be recommended to get an updated version as otherwise, you would need to do the code upgrade yourself in another development layer. Updating to the correct version in the future would be quite impossible if you try to do it yourself. It would also save you from a lot of responsibilities and risks. If you encounter bugs after upgrading the ISV solution yourself, you can't knock on the door of the ISV...
Question 2:
There is an impact analysis which will list the objects which has changes before you do the actual update. Also ensure, the baseline database will be created correctly which will help you doing a comparison between new and old.
Hi s14raj,
Regarding your ISV solution, you will need to reach out to your ISV provider and ask him for a compatible version for AX 2012 R3.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (