Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Hello, I am going to be performing an upgrade of CRM 2011 with ADX 6 to CRM 2016 which I believe will require ADX to be upgraded to ADX 7 as 6 is not supported on 2016. Both are On-Premise.
Based on information on the website it sounds like the upgrade path looks something like this
- Upgrade CRM 2011 all the way to CRM 2016, still ADX 6- Upgrade ADX 6 to ADX 7 as per standard upgrade steps.
I saw this thread where another user had to remove ADX completely from 2011 before upgrading CRM. community.adxstudio.com/.../c65315af-8402-e611-9406-000d3a10ca82
By default I am going to attempt the above upgrade path, and only resort to the second approach if necessary, but is there any official documentation on doing an upgrade like this? Does anyone know whether issues happen frequently enough that it's recommended to actually go with the second approach to begin with? Would like to know what other's experience with this process is for insight.
Do you have the ADX v6 "Complete Solutions" or the various ADX v6 solutions for different portal components?
I had an issue where it failed to load some of the v7.0.0022 components because of a known issue with replacing the TinyMCE with the CKEditor using the ADX v6 "Complete" solution. I was able to replicate this on test system as well. (Upgrading to v7 where v6 was the different component solutions seemed to work better)
After many headaches, I ended up having to upgrade first to v7.0.0021 (still used TinyMCE) then REMOVE ADX v6 Complete Solution and then upgrade to ADX v7.0.0022, this worked with no issues and no loss of portal metadata.
Note that the ADX v7 installer will pull the latest solutions from the web, so to upgrade to v7.0.0021, you need to import the solutions directly.
Ideally you want to be able to not to have to remove ADX v6 *before* you upgrade to ADX v7 because you will lose all your portal metadata and have to re-import/rebuild it.
Note that you cannot install ADX 6 on CRM 2016, but if you upgrade CRM to 2016, ADX 6 will still continue to work on CRM 2016 (unsupported), so that might give you some phasing/staging options.
With any upgrade, you always want to do a test run first!
I hope this info helps.
Thanks for the quick response Nick. Yes we do have the ADX v6 complete solutions installed (6.0.0029) in CRM 2011, and I also see some of the other solutions installed 6.0.0011.
This is extremely helpful, regardless of what issues I may or may not encounter, you've brought up three very important points that I was not aware of. Very glad to know that there is a possibility of avoiding a migration.
Business Applications communities