Microsoft Dynamics 365 | Integration, Dataverse...

Solution Import - missing dependencies

(0) Share

Report

Posted on by sam hajjar

Hello Community,

I am running into a problem of trying to import a solution that I have exported from one Dynamics 365 instance (Development instance) to another Dynamics 365 instance (Test instance, managed solution). The problem is the system is complaining that the destination environment is missing components that are used as dependencies in the solution. However my solution does not contain the components mentioned in the import dialog.

Details:

In my DEV instance I have a solution SCRIPT with web resources only, I accidentally added an entity (entity A) to the solution but removed it afterwards (no more entity components in my solution)

When I try to export this solution as managed and import it into my TEST instance (TEST doesn't have entity A) I get the missing dependencies dialog with Entity A as missing component.

I don't have Entity A in my solution why is it considering it required by the solution?

Is this a bug or am I missing something?

On-premise environments Microsoft Dynamics 365 Version 1612 (9.0.31.7) (base de données 9.0.31.7)

Your help is much appreciated

Thank you.

Sam

I have the same question (0)

All responses (9)

Answers (0)

Luke Thomas on at

Like (0)

Report

Are you sure that when you accidentally added the entity to your solution, it did not add additional dependencies such as model driven apps, client extensions, plugins, etc.? If you look at the components view of your solution, does it only show 'Web Resource' type components?

Was this reply helpful? Yes No
sam hajjar 25 on at

Like (0)

Report

Positive, only web resources in the solution.

Was this reply helpful? Yes No
Luke Thomas on at

Like (0)

Report

Was there a time when the solution was exported as managed to TEST with the 'missing' entity in it?

Was this reply helpful? Yes No
sam hajjar 25 on at

Like (0)

Report

No, the solution is usually dedicated for web resources. When I accidentally added the entity to it, I removed it directly and so it was never exported with the entity

Was this reply helpful? Yes No
Luke Thomas on at

Like (0)

Report

Have you tried incrementing the solution's version number when migrating to TEST?

Was this reply helpful? Yes No
sam hajjar 25 on at

Like (0)

Report

Yes I did. I also checked the Solution.xml file and it includes all the components of the entity I removed in <missingdependencies> . I tried the same procedure on a Dynamics 2015 instance and it had a different behavior:

In my script unmanaged solution I added an entity (entity A), published, removed entity A then exported the solution and was able to import it without any issues on a TEST instance not containing entity A.

It seems to me this is a bug in my v9.0 version?

Was this reply helpful? Yes No
Luke Thomas on at

Like (0)

Report

Could be a bug....If all else fails you could delete the missing dependencies in the solution.xml and re-zip the solution to import. Of course, this is unsupported (but has worked for us in the past).

Was this reply helpful? Yes No
Suggested answer

sam hajjar 25 on at

Like (3)

Report

We found the solution:

Missing dependencies when you try to import a solution only with WebResources.

Going into the DB, we found some orphan dependencies for forms that were added before on the entities that you removed.

The solution was to introduce the entities again, remove the forms, publish, remove the entities and publish again.

After performing this step, the solution was exported and imported without any issue.

Was this reply helpful? Yes No
Luke Thomas on at

Like (1)

Report

Very strange! You would think when you remove entities from a solution, the system would know to remove the child dependencies...Glad you found the solution though! I will have to keep it in mind for the future.

Was this reply helpful? Yes No