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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

multiple managed solutions with dependancies on each other

(1) ShareShare
ReportReport
Posted on by

Hi Everyone,

So here's a dilemma I'm struggling with...

We have multiple environments all with the same solutions in.  Our dev environment has an unmanaged solution with our customisations in. Plus several managed solutions from various 3rd parties.

when we promote the dev solution to test or production, we export it as a managed solution.

the problem i've got is i am trying to remove one of the 3rd party managed solutions.  

Starting at dev i removed all the dependencies for the managed solution to another managed solution and to our unmanaged solution, by moving the code etc into the unmanaged one., removed the 2 managed solutions... all was fine 

i then promoted our customization as an unmanaged solution up to test and then tried to remove the unmanaged solutions.

1 went without a problem, so i know the java dependencies are now all gone,  but the other has got some very strange dependencies to our now managed solution which contains our customisations.  

First of all localizedlabel dependancies like here

www.crmcodex.com/.../this-solution-cannot-be-uninstalled-because-the-localizedlabel-with-id-form-is-required-by-the-solution-uninstall-the-solution-and-try-again

fine.... I ran the sql, it removed the dependencies,

but then appears more dependencies on systemforms.

firstly and probably the the interesting thing to find out is how come it ended up that 2 managed solutions can become so dependent on each other, it shouldn't be possible.  i'm thinking one was changed to managed out of sequence somehow in the deep distant past and caused the issue.

Secondly I wonder if there is anyway out of it so we can end up having removed the 3rd party managed solution.

I'm way into unsupported territory here that we are looking at other solutions,  i just want to try and do it since i've poked my headinto the rabbit hole, might as well jump in and run round the warren like.

Any ideas anyone?

Cheers


Chris

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    Figured it out, plug in's registered from one solution to fields in the other.  Simple really.

  • Suggested answer
    Gopalan Bhuvanesh Profile Picture
    11,401 on at

    It is a best practice to create Dependency Document, so that the developer would update it during the development.

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…

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