Best practice working with Solutions

(0) Share

Report

Posted on by Community Member

Hello everyone,

I currently work with CRM 2001 with multiple solutions (ClickDimensions, different vendors, few internal), and I must say it's a nightmare.

Solutions are referencing each other, so when it's time to change the code, or schema (in one or more) and then to import from one env to another, we have so much problems. They often fail to import because of various reason (dependencies, missing fields, etc). Also sometimes asme fields become visible on the form multiple times (I guess because of form merging issue).

So I was wondering what is the best practice working with solutions? Do you separate schema from code, or you pack everything in one? Do you work with managed or unmanaged?

Thank you

Mihailo

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Community Member on at

Like (0)

Report
Copy link

Link copied!

I would try to limit the number of unmanaged solutions - I usually only have 2 (main customization and a custom ribbon one if I'm using the Ribbon Workbench). I recommend this because of how solutions "build" on each other.

There is the system solution which is then modified by managed solutions which is then modified by unmanaged solutions. So the most flexible is unmanaged. There's an excellent image in the following link:

msdn.microsoft.com/.../gg334576.aspx

Was this reply helpful? Yes No
Suggested answer

Amar Prakash 565 on at

Like (1)

Report
Copy link

Link copied!

The best approach is to use Managed solution for a production environment. But in some of the scenarios Manged solution does not work properly. So in your case, you can go ahead with a unmanged solution. Thanks.

Was this reply helpful? Yes No
Suggested answer

Neil Parkhurst 10,727 User Group Leader on at

Like (1)

Report
Copy link

Link copied!

Some if your solutions such ClickDimensions will be managed in all environments. As provided by the supplier. For your own solutions develop them as unmanaged but deploy to production as managed. Always deploy your supplier solutions like ClickDimensions first then your own second. That should help avoid some of the conflict messages you describe. I believe you are 2011 at the moment if/when you migrate to 2016 this approach will prepare you ready to use patch management etc available in 2016. (which improves solution management quite a bit)

Was this reply helpful? Yes No