Best practices for solutions in Dynamics CE

(0) Share

Report

Posted on by Fkr1987

209

Hello people,

We have started with Dynamics and have a test&production instance. Which is the best way to work with solutions and deployments, what are your best practices, and tips&trix?

I was thinking about having an unmanaged solution in Test where i do the customizations and then importing it to production? is that the right way? And when doing new things i can just use the same solution. If we have partners who work with our enviroment, should they have their own prefix and solution?

What are your strategies to have a really smooth process of deployments and maintence of solutions in Dynamics CRM?

Thankful for feedback :)

I have the same question (0)

All responses (3)

Answers (2)

Verified answer

Priyesh 7,396 User Group Leader on at

Like (0)

Report

Hi,

To follow a clean path of development and deployment, I suggest you review this -

d365demystified.com/.../

Hopefully this will get you started. And then you can scale up implementations in sprints

Was this reply helpful? Yes No
Suggested answer

Gilmeyer on at

Like (0)

Report

Hi,

We recommend to read our documentation Solution Lifecycle Management: Dynamics 365 for Customer Engagement apps.

Which can be found in www.microsoft.com/.../details.aspx

Thanks,

Was this reply helpful? Yes No
Verified answer

gdas 50,091 Moderator on at

Like (0)

Report

For me solution patch should be good idea if you really want to deliver managed solution in prod instance. If you have only one environment for TEST and DEV so keep all customization in one solutions and by default all components will be unmanaged.

Managed and unmanaged solution both have advantages and disadvantages but remember managed solution is good when you completed your development and want to deliver it to production.

I suggest to read below article before make the decision.

https://www.itaintboring.com/dynamics-crm/managed-solutions-vs-unmanaged-solutions/

I dont see any reason to have multiple prefix if you are working in same project and maintain proper documentation , you can always create different prefix if you really need to differentiate solutions component .

Was this reply helpful? Yes No