Can anyone help me to version issue with Dynamics crm plugins. I have developed plugin in Dynamics 365, But it is not working in Dynamics CRM 2015 online.
Can i create a package which will work in all dynamics CRM versions?
*This post is locked for comments
Hi,
As suggested by Nadeeja, solutions exported from an earlier version of Dynamics 365 can be imported into later versions and not to earlier versions.
Hi Nithya,
I am bit cofuse with you answer, Using the Assembly Versioning concept, Can I import solution in Dynamics CRM 2015 online which is created in Dynamics 365 Online.
I am using export import method to do this and getting issue.
Thanks Nadeeja,
Actually my issue is i have developed plugin in Dynamics 365 online, and my company got a lead which has requirement to install plugin in Dynamics CRM 2015 online.
Is there any possible way to this? I don't have Dynamics CRM 2015 online license, i can not even recreate plugin in Dynamics CRM 2015 online.
Hi pbb,
If you created the plugin in Dynamics 365 (8.2) and trying to import that solution to an older version of Dynamics CRM, it won't work. See the version compatibility matrix.
msdn.microsoft.com/.../gg334576.aspx
Also check this important blog post from Dynamics 365 Team regarding backwards compatibility of SDK.
community.dynamics.com/.../dynamics-365-sdk-backwards-compatibility
Hi,
For this, you should know about Assembly Versioning.
Plug-in assemblies can be versioned using a number format of major.minor.build.revision defined in the Assembly.info file of the Microsoft Visual Studio project. Depending on what part of the assembly version number is changed in a newer solution, the following behaviour applies when an existing solution is updated through import.
The build or revision assembly version number is changed.
This is considered an in-place upgrade. The older version of the assembly is removed when the solution containing the updated assembly is imported. Any pre-existing steps from the older solution are automatically changed to refer to the newer version of the assembly.
The major or minor assembly version number, except for the build or revision numbers, is changed.
When an updated solution containing the revised assembly is imported, the assembly is considered a completely different assembly than the previous version of that assembly in the existing solution. Plug-in registration steps in the existing solution will continue to refer to the previous version of the assembly. If you want existing plug-in registration steps for the previous assembly to point to the revised assembly, you will need to use the Plug-in Registration tool to manually change the step configuration to refer to the revised assembly type. This should be done before exporting the updated assembly into a solution for later import.
Refer the links below.
gonzaloruizcrm.blogspot.in/.../assembly-versioning-in-crm-2011.html
msdn.microsoft.com/.../gg309620.aspx
Hope this helps you.
#1
André Arnaud de Cal...
292,494
Super User 2025 Season 1
#2
Martin Dráb
231,305
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
