Export a solution for a specific CRM version
Applies To: Dynamics CRM 2016, Dynamics CRM Online
This topic describes functionality that is available for minor version updates to major versions of Microsoft Dynamics CRM. This capability is not available for the initial release of Microsoft Dynamics CRM Online 2016 Update and Microsoft Dynamics CRM 2016 (on-premises), but will be when minor version updates included additional functionality.
Each new version of Microsoft Dynamics CRM will contain capabilities not found in earlier versions. Solutions that use new capabilities can’t be imported into an earlier version organization. Solutions exported from older version organizations can be imported into newer version organizations.
After you upgrade the organization you use to define your solution, you can still export a solution that targets an earlier version. When you select a lower target version any solution components that depend on capabilities introduced since that version won’t be included in the solution you export.
You can’t select an earlier version when you export the default solution.
When you export a solution from Microsoft Dynamics CRM Online 2015 Update 1 you will have the option to target the solution for a specific CRM version. For Microsoft Dynamics CRM Online 2015 Update 1 the options are 7.1 (default) and 7.0. When you choose 7.0, any new capabilities introduced in Microsoft Dynamics CRM Online 2015 Update 1 will not be included in the exported solution and any organizations still using earlier versions of CRM 2015 will be able to install the solution.
When you export your solution to target an earlier version the export dialog can display two possible messages:
- This solution supports the target CRM version
This means that the solution components in your solution don’t depend on any capabilities or solution components introduced since that version.
- The following components are removed or modified as part of the export
Below this message a table lists the solution component items that were modified or not included in the exported solution.
The information visible in the dialog can also be found in the exported solution file. When you export a solution to target a specific version, the name of the file will specify the target solution using the following naming convention:Solution Name_Solution_Version_Number_target_CRM_Target CRM version number.zip. For example, an unmanaged solution with the name Sample Solution with solution version 2.0 that is exported to target the version 7.0 will have the name SampleSolution_2_0_target_CRM_7.0.zip. When you extract the contents of this compressed file you will find a filteredcomponents.xml file containing data detailing which actions were performed. You can open this file using Excel to view a report of which solution components were edited or removed.
Starting with the CRM 2013 and Microsoft Dynamics CRM Online Fall ‘13 releases, each type of solution component has an IntroducedVersion property. This value captures the current version number of the solution that the solution component was associated with when it was created. All solution components introduced by Microsoft are part of a hidden system solution where the version number corresponds with the Microsoft Dynamics CRM version.
Solution components introduced
Before CRM 2013 and Microsoft Dynamics CRM Online Fall ‘13
CRM 2013 and Microsoft Dynamics CRM Online Fall ‘13
Microsoft Dynamics CRM 2013 Service Pack 1 (SP1) and CRM Online Spring ‘14
Microsoft Dynamics CRM 2015 and Microsoft Dynamics CRM Online 2015 Update
Microsoft Dynamics CRM Online 2015 Update 1
Microsoft Dynamics CRM Online 2016 Update and Microsoft Dynamics CRM 2016 (on-premises)
The IntroducedVersion data is used when exporting the solution to match the target version. This can result in three possible actions:
Solution components that did not exist in the target version or contains dependencies on components that can’t work with the target version won’t be added to the solution.
When a solution component has a dependency on a solution component that is removed, when possible, the solution component will be modified to remove the dependency. For example, if a form definition references an attribute that did not exist in that version; the form will be modified to remove that reference. If the solution component cannot be modified to remove the dependency the solution component will be removed.
When a solution component existed in the targeted version but was modified to have a dependency on a solution component that will be removed, that solution component may be replaced with the definition of the solution component that was defined for the targeted version.
Microsoft Dynamics CRM 2016 and CRM Online
© 2016 Microsoft. All rights reserved. Copyright