web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Approach for Managed S...
Microsoft Dynamics CRM (Archived)

Approach for Managed Solution in CRM Organization

(0) ShareShare
ReportReport
Posted on by Rahul-Waghmare 990

Hello All,

We are planning to change the practice of importing unmanaged solution on Production environment.

Till date we have all the solutions as a umnanaged in production, now going onward we would like to import only managed solutions which will be easy to manage on production so that we can rollback the changes whenever required.

What should be the best possible approach that we need to follow here, as we cannot import the managed components over unmanaged components. And if we are moving single component as a managed without adding its dependent component, it will throw an error -missing dependent components while import.

Regards,
Rahul

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Aiden Kaskela Profile Picture
    Aiden Kaskela 19,696 on at

    Hi Rahul,

    In your current situation, you hit the nail on the head with the problem and it doesn't leave a lot of choices (in 2013 at least). In 2016 you can include only components into a solution so you wouldn't have the problem as much, but it'll still happen. There might be some database hacks you can try but it's always risky and when you upgrade you could see all kinds of problems.

    If you're serious about only deploying managed solutions and you have unmanaged fields on both, you need to create new fields and when you roll out, copy the data from the old fields into the new managed ones then delete them. It's going to be a nightmare no matter what.

    I came into a similar situation recently and we're continuing to use unmanaged solutions for the internal customizations but creating a backup solution on production before we roll out. It wouldn't delete any new fields but the forms and labels will revert and that's what most users see.

    Hope this helps! I'd appreciate if you'd mark this as Answering your question.

    Thanks,

     Aiden

  • Verified answer
    Rahul-Waghmare Profile Picture
    Rahul-Waghmare 990 on at

    Thanks Aiden for your reply.

    "You hit the nail on the head with the problem" this was the first line struck in my head when my manager asked to go with Managed solution approach on unmanaged layer. :)

    Yes, I got your 2nd point to take the backup every-time new solution goes live, that's the same practice we are following till date for every release we need to take backup database and solution.

    What I am thinking here to create new organization of production and start importing managed solution on to it, will it be a good approach or there are any challenges to this.

    Regards,

    Rahul

  • Verified answer
    Aiden Kaskela Profile Picture
    Aiden Kaskela 19,696 on at

    Hi Rahul,

    It's a really good approach as far as getting managed customizations but you'll need to migrate all your data and that could be painful. If you start with a brand new org, you'll need to update all the fields that reference Owner ID to the new owner and map a lot of system data like transaction currency id, organization id, uom id, etc..

    Another way you could go with it is to start with a redeploy of your production org so it has all the same IDs for the setup records. Delete your unmanaged fields either individually or programmatically and import managed solutions over it. Then you can delete all the non-setup data (contacts, account, activities, etc) and when you're ready to switch over, migrate the data from old to new org. Since you're keeping all the same field names, Migration Dynamics from Cobalt would be ideal for moving the records and I'd definitely use it in that case. If you're move of a DIY guy, and you didn't hear it from me, but you may want to look at moving your data in SQL. It's lightning fast and if your system IDs and fields are the same it's going to be relatively easy. There's a lot of tables you need to get right but I may have done it once or twice and it's a really good way to go if you know what you're doing.

    Hope this helps! I'd appreciate if you'd mark this as Answering your question.

    Thanks,

      Aiden

  • Rahul-Waghmare Profile Picture
    Rahul-Waghmare 990 on at

    Thanks Aiden,

    Yeah, I have gone through the Migration Dynamics Webinar video from youtube. That would be great if users can continue to use their current CRM organization while migrating the data to new organization. I will have words with Customer on this.

    Thanks for your help and briefing about the approach.

    Regards,

    Rahul.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans