Solution patching in unmanaged

(0) Share

Report

Posted on by DlwK

607

In this technet article, I have read some guidelines from MS about Solution patching: https://technet.microsoft.com/en-us/library/mt628808.aspx

One of the guidelines is that you shouldn't use solution patches in unmanaged production environments. What could be the reason not to do this? I know that you cannot rollup the patches by importing an upgrade solution (clone solution). But what you can do is do the Clone Solution action on the unmanaged production environment, and then import the cloned solution from development?

Unmanaged is advised for production environments of your own (non-isv business env.)? Or would you still adivse managed for this?

Kind regards

Kim

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

yogesh_890 5 on at

Like (0)

Report

RE: Solution patching in unmanaged

Hi Gautam,

I have been working on ALM for Powerapps currently. I found your suggestion quite useful but

can't we use one instance to develop patch as unmanaged and then clone it with main solution. From here it can be exported as managed and imported to Production environment as upgrade. In this way we can always maintain production as managed.

Thanks

Yogesh

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (2)

Report

RE: Solution patching in unmanaged

Hi Kim,

you shouldn't use solution patches in unmanaged production environments. What could be the reason not to do this?

There is many reason not to use production environment unmanaged. Doing unmanaged in production means you are working with the default solution , you can not uninstalled your solution in future , if any issue happen in production environment. There may be many reason you can check out here -

https://msdn.microsoft.com/en-in/library/gg334576.aspx

But what you can do is do the Clone Solution action on the unmanaged production environment, and then import the cloned solution from development?

When you are doing clone that means it will take reference from all solution pathces , and creating one solution so its a right way to move unmanaged and managed solution. This is the way solution patching is working in Dynamics 365. Let say you have multiple patches and and your production envirnment is having old patches , so you may need to upgrade 3 ,4 patches together. In that case solution cloning is came into picture. So do always solution cloning to take all reference and deploy the solution ans managed or unmanaged.

Unmanaged is advised for production environments of your own (non-isv business env.)? Or would you still advise managed for this?

No , I would suggest to make your production instance as managed solution , if you are doing unmanaged means you are making production environment as unmanaged . I agree that you can not change the component directly in production but , as a good practice you should go for managed solution for your production environment . Considering your customer will not customize directly in the production instance in future.

Hope this helps.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

RE: Solution patching in unmanaged

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.

Was this reply helpful? Yes No
Mahendar Pal 45,095 on at

Like (0)

Report

RE: Solution patching in unmanaged

In additional that in earlier version, un-managed solution also used mostly for own production servers because it was easy to remove some component if you deployed there by mistake or because of some other reasons and there was not a direct out of the box way to remove those components if you have used managed solution. But now you can remove components from Managed solution by releasing patches as well.

Thanks

Was this reply helpful? Yes No
David Jennaway 14,065 on at

Like (0)

Report

RE: Solution patching in unmanaged

It's difficult to give a definitive answer. The Microsoft advice has always been to only used managed in production, but in practise in earlier CRM versions there were bugs and limitations with the solution infrastructure that could cause significant problems with managed solutions, so many implementations used unmanaged in production.

Since CRM 2016, all significant issues have been resolved, so using only managed solutions in production should not cause problems. On the other hand, the main benefits of managed solutions are to allow uninstall, and to restrict what can be changed via managed properties, and if you don't intend to use these, then you could use either managed or unmanaged in production

Was this reply helpful? Yes No