Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics CRM (Archived)

Maintaining a unmanaged solution in Production

Posted on by 15

Hello,

I created a solution and made the deploy to the production environment, but when doing so, I did it as a unmanaged solution. Now I need make some adjustments to this solution (Creating new fields, creating new business rules...), what is the best/recommended way to proceed? Keep in mind that I'll be making a lot of adjustments/adding new things. I'm planning on doing one deploy/version per week.

1) Delete the imported solution and when importing the v2.0 import it as a managed solution and keep updating it?

2) Keep the unmanaged solution and keep making the changes on it?

Thanks for your help!

*This post is locked for comments

  • Dynamics365 Rocker Profile Picture
    Dynamics365 Rocker 7,755 on at
    RE: Maintaining a unmanaged solution in Production

    Make changes in your dev environment and import these changes as unmanaged or managed solution in production.

  • Suggested answer
    Kokulan Profile Picture
    Kokulan 18,048 on at
    RE: Maintaining a unmanaged solution in Production

    Hi

    Since you have already deployed the components to Prod as Unamanaged, there will be components on Prod in Unmanaged state. Deleting the solution will not change their state.

    if you are to follow step 1, when you import the managed solution, you will get error saying the components already in Unmanaged state. To resolve this, you may end up deleting these components  which also means you may lost data in if you delete any fields.

    If this solution is internal to your company, not something you are selling to your customers, I would go for Option 2. Keeping solutions Unmanaged all the way through to Prod does give you a lot of flexibility besides, for internal or in-house solutions staying unmanaged it not a bad option.

  • Suggested answer
    T.I.A Profile Picture
    T.I.A 1,760 on at
    RE: Maintaining a unmanaged solution in Production

    It would be better to do the first option. It's best practice to do you changes (processes, customisations etc) and deploy them to production when you are ready.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans