Circular dependency between solutions

(0) Share

Report

Posted on by KoJaPD

601

Hi,

I have two unmanaged solution, where the second solutions builds additional stuff on top of the first solution. However, when I try to export and import the first solution as a managed solution into a production environment, a dependency error is thrown that stuff from the second solution is missing...

How can I check why this happens?

In the second solution I add for example a new entity, that has a lookup field to another custom entity that originates from the first solution...

Categories:

Governance & administering

I have the same question (0)

All responses (4)

Answers (0)

KoJaPD 601 on at

Like (0)

Report
Copy link

Link copied!

It drove me crazy... it seems that the second solution had a different publisher than the first solution, once I changed it so both solutions have the same publisher, the problem went away... ?!?!?

Was this reply helpful? Yes No
KoJaPD 601 on at

Like (0)

Report
Copy link

Link copied!

I was too early to cheer... still driving me crazy...
In SolutionA I have CustomEntityA; in SolutionB I have CustomEntityB with a lookup field to CustomEntityB.
When I now try to import the managed SolutionA into a production environment, it says that a dependency on CustomEntityB is missing in solution "Active"... 😞 😞 😞

Was this reply helpful? Yes No
eleung83 232 on at

Like (0)

Report
Copy link

Link copied!

Yep you'll need to combine any entities that have dependencies on each other in the same solution. You also have an option to add all required objects attached to an entity when you include an entity in a solution (it could potentially add a lot of extra objects as it would be as if you were deploying the solution to brand new environment with no customisations).

One way you could minimize the work is by only adding the components of the entity to the solution , but this only works if both entities exist in your target environment. For Example if you have created a lookup to CustomEntityB in CustomEntityA, then you can just add the lookup field and the relationship when you add CustomEntityA to your solution. But if you have not yet created both entities in your target environment this won't work.

If you're using ADO to do your import/export then there are a couple of custom build tasks in https://marketplace.visualstudio.com/items?itemName=WaelHamze.xrm-ci-framework-build-tasks (Get Solution Missing Components, Get Solution Missing Dependencies) that are still in preview, so may report more issues than you would expect. Unfortunately I don't think there's any other UI that informs you of missing dependencies until you attempt to import the solution into the target environment

Was this reply helpful? Yes No
KoJaPD 601 on at

Like (0)

Report
Copy link

Link copied!

Hi, I am still banging my head to why SolutionA gets "corrupted" when I add a lookup in SolutionB.

It happens even when I create a simple new SolutionC with a new simple CustomEntityC that has a lookup to the standard entity Account. In solution.xml for SolutionA appears a missing dependency to CustomEntityC from solution "Active"...
It seems that somehow having multiple solutions that lookup a common entity is creating problems...

Was this reply helpful? Yes No