Missing Components

(0) Share

Report

Posted on by Community Member

I'm trying to import a tried and tested solution into a new clean Sandbox environment that has recently been upgraded to 2016. I was able to successfully install this solution in another Sandbox on the same tenant unmanaged, and this is the first time I'm trying to import it managed in 2016. The solution is telling me that components are missing from the system, but they definitely aren't! Has anyone else come across this issue in CRM 2016?

This only occurs for fresh managed installs, not for upgrades or unmanaged environments.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Community Member on at

Like (0)

Report

Can you send a list of the missing components?

Few things to try community.dynamics.com/.../150502

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Unfortunately the suggestions haven't worked, but thanks for sharing. The components all relate to the Contact form, and this form with all dependencies have been previously deployed.

Components listed are EntityRelationship, View and Entity which I've all confirmed exist in the environment as Managed components.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Have you read through this?

https://msdn.microsoft.com/en-us/library/gg309749.aspx

Additionally, when you import a managed solution all required components must match the package type of the solution. A component in a managed solution can only depend on another managed component.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for the link - everything here checks out, and all components are managed.

Was this reply helpful? Yes No
Suggested answer

razdynamics 17,308 User Group Leader on at

Like (0)

Report

HI Aaron I came across a similiar problem recently where solution import worked where there was data / system jobs but failed in a clean environment. What you need to do is get the MS Support Team to run a Trace log on the server whilst performing the import and this will identify some conflicts on field names on a specific form, once we identified the conflicting field we removed it and replaced it with another one with a slightly different name and the import worked. This problem usually occurs when you replace a field which has the same name but differnt field type.

Good luck :)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Hi Raz,

I'm encountering a similar issue with a Dynamics 365 on-premise tenant. I have 2 managed solutions:

one contains entities, fields and forms

the other solution contains only workflows, some of which have dependencies on fields in the first solution

I can successfully import the first managed solution into a clean environment, but the managed workflow solutions fails every time saying that the dependent fields are missing. However these fields are not missing from the target system as I can navigate to them and interact with them on the forms.

Do you have any ideas?

Was this reply helpful? Yes No

Community site session details

Missing Components

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Featured topics

Product updates

Community site session details

Missing Components

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Featured topics

Product updates