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 can not update base solution, if it is patched.
Delete a Patch or Base Solution:
In the above example we have created two solutions (Solution-A and Solution-B). B is the patch for A and higher in version. To delete a base solution (Solution-A)
Unmanaged : Then Solution-B must be deleted first then Solution-A
Managed: Solution-A can be deleted directly, Microsoft dynamics will remove all the patches in order from higher to lower version.
Delete a Patch or Base Solution:
In the above example we have created two solutions (Solution-A and Solution-B). B is the patch for A and higher in version. To delete a base solution (Solution-A)
Unmanaged : Then Solution-B must be deleted first then Solution-A
Managed: Solution-A can be deleted directly, Microsoft dynamics will remove all the patches in order from higher to lower version.
I really appreciate information shared above. It’s of great help. If someone want to learn Online (Virtual) instructor lead live training in MICROSOFT DYNAMICS CRM kindly contact us http://www.maxmunus.com/contact
ReplyDeleteMaxMunus Offer World Class Virtual Instructor led training on MICROSOFT DYNAMICS CRM We have industry expert trainer. We provide Training Material and Software Support. MaxMunus has successfully conducted 100000+ trainings in India, USA, UK, Australlia, Switzerland, Qatar, Saudi Arabia, Bangladesh, Bahrain and UAE etc.
For Demo Contact us.
Saurabh Srivastava
MaxMunus
E-mail: saurabh@maxmunus.com
Skype id: saurabhmaxmunus
Ph:+91 8553576305 / 080 - 41103383
http://www.maxmunus.com/
Patching doesn't work with solution components with unmanaged customization. A patch fails to overwrite these unmanaged customization with changes defined in patch until solution upgrade. Even after the solution upgrade with overwrite unmanaged customizations this solution component remains to have an entry in active solution hence this solution component shall not be useful for subsequent solution patching as well. The only permanent solution is to create a new managed solution component in place of this and refer it at all places required then remove the old one. Before opting for patching as means of your solution development ensure you do not have any unmanaged customization that would participate in patches before hand to avoid solution upgrades after every patch import.
ReplyDelete