Solution - Clone a Patch in Microsoft Dynamics CRM 2016

abhishek_255

1,612

Like(0)

Report

To perform and release customization in CRM from one system to another, usually we create "Solution", once done with customization(s) we export it either managed or unmanaged and deploy it to production.

Suppose a scenario where we have created a Solution (Solution-A), in that we have done some changes [added a new field say "new_field" length 50 for a entity] and deployed it to production.

Due to some reason now the requirement is to change the field length from 50 to 100. In earlier version to achieve it, either we directly update the field length in production or create a new solution (Solution-B) with all the changes and deploy it on production.

To overcome this situation Microsoft Dynamics CRM 2016 introduces new feature "Clone a Patch". In which you can release fixes for the solution(s). In this scenario we can create Patch "Clone Patch" for Solution-A.

Benefits:

A. You can only create a patch Solution from a base Solution.

B. Patch solution can not be further patched.

C. There could be N no of patches from base Solution.

D. You can not install a patch if base solution is not available.

E. Patch solution version must have higher build and revision numbers and same major and minor version than base solution version.

F. Patches are only supported in CRM organizations of version 8.0 or later.

G. You cannot remove component from base solution.