Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am upgrading from ax 2009 sp1 to ax 2012 r3 cu13, During AX 2009 go-live, we have installed one bus/ISV solution, but that never used.
Now we do not have AX 2012 upgraded model of that ISV, what should be the way forward.
If I try to go without this ISV, is it a correct approach.
ISV name : ()
If you're 100% sure that no part of the ISV silution is used, remove it from AX 2012 (and fix any potential conflicts). It seems that you should have done that a long time ago.
Thank you so much for your help.
ISV get installed long back around 2011 during go live, but never used.
Code upgrade, I will try to resolve if any conflict comes manually.
I am more concern about data upgrade, not sure how does this ISV will impact, I have verify and there are no data in any customized table used by this ISV solution.
One more thing does AOT objects related to this ISV required any kind of special treatment during "Preserve legacy element IDs" or just leave them.
No, you don't have to worry about data upgrade if you're saying that there is no data. When you remove the ISV solution, all its tables and fields will be removed, therefore there won't be anything to upgrade - no data and no elements whose IDs you could worry about.
Business Applications communities