Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
So I just imported a managed solution built off of 2011 into CRM 2015 on premise. I
received the attached error. My question is how is an upgraded CRM from 2013 to 2015 going to handle these solutions and will they break?
The error message states that you cannot import a CRM 2011 solution. So the managed solution seems not compatible with CRM 2015.
However, the version compatibility says "You can install solutions exported from Microsoft Dynamics CRM 2011 and earlier releases of Microsoft Dynamics CRM Online into Microsoft Dynamics CRM 2015 and Microsoft Dynamics CRM Online 2015 Update. "
Would like to know what the CRM support team says. Should it be CRM 2013 instead of CRM 2011 as a compatible version?
That was a mistake in the SDK - solutions exported from CRM 2011 won't be able to be imported into CRM 2015.
CRM 2011 solutions imported into a CRM 2013 environment will function as expected (assuming they use CRM 2015 supported methods) when the organization is upgraded to CRM 2015.
If you have a 3rd-party managed solution that cannot import from 2013 Online to 2015 (I tried this in my sandbox), I am guessing our best bet is to contact this (now ex-)vendor for an update...in other words, since we no longer need/use this managed solution, we'll probably need to pay them to get a solution to the incompatible solution.
After re-reading this a few times this weekend, I am reading this: if you have a 2011-compliant solution correctly installed and then upgraded to 2013, then this solution should work as long as the vendor used CRM 2015 supported methods. So, I guess my concern is to find out if this vendor did use those methods.
If I am reading this correctly then, I should be able to upgrade my production instance to 2015 if the previous paragraph works out, even though I cannot import/install this particular solution in to a 2015 sandbox (this solution fails with the error like LLB's)
Business Applications communities