Export Solution Missing Required Components: entity required by itself

(1) Share

Report

Posted on by kevin.dynamics

we are using Dynamics 365 online latest version 9.1.0.17461. We created a solution and only added one existing entity called "Approval" with a subset of its fields. When exporting the solution, it shows below "Missing Required Components" dialog. The error message says it is missing the "Approval" entity, which is the only entity we added in the solution

Since we don't want to add all the other dependent entities that downstream environments do not need, so "Add all assets" is not an option for us. We did try the following approach but nothing works.

with/without including entity metadata when exporting the solution
without "adding all the assets", but manually added all the forms/views/field

Also, there is no lookup field in Approval Entity that is pointing to itself.

Any idea of what is missing? Thanks.

I have the same question (0)

All responses (11)

Answers (1)

SamiraM 587 on at

Like (0)

Report
Copy link

Link copied!

Hi Kevin,

Please remove the entity from the solution and add it again. You can un-check all metadata and all assets checkbox. Then add the fields that you want to import.

In the final step it will ask you to import required components. Add these required component then you will be good to go.

Regards,

Samira

Please mark it verified if it answer your question.

Was this reply helpful? Yes No
Vaibhav Shukla 120 on at

Like (0)

Report
Copy link

Link copied!

Hello Kevin,

Are you using any global option set on Approval entity?

If Yes, Please add that global option set to the solution if not you can go with approach suggested by @Samira Mirza.

Hope this helps! I'd appreciate if you'd mark this as a Verified answer.

Thanks,

Vaibhav

Was this reply helpful? Yes No
Verified answer

Ragnar Hilmarsson 3,427 on at

Like (0)

Report
Copy link

Link copied!

You can manually remove the missing dependencies from the solution.xml file after you have exported from your source env, the xml look like this

</RootComponents>

<MissingDependencies />

</SolutionManifest>

</ImportExportXml>

I've used this:

blog.thenetw.org/.../

Was this reply helpful? Yes No
kevin.dynamics 10 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the reply. But this doesn't work for us. "Add required component" will add all the fields. After that it seems there is no "remove subcomponent" button availabe anymore to remove the fields we don't need.

Was this reply helpful? Yes No
kevin.dynamics 10 on at

Like (0)

Report
Copy link

Link copied!

There is no global optionset for this solution.

Was this reply helpful? Yes No
SamiraM 587 on at

Like (0)

Report
Copy link

Link copied!

Have you unchecked the all assets and all metadata checkbox?

Was this reply helpful? Yes No
kevin.dynamics 10 on at

Like (0)

Report
Copy link

Link copied!

I did. :-(

Was this reply helpful? Yes No
kevin.dynamics 10 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the link. I manually removed the missing dependencies from the solution.xml, and I got the following error when importing the solution. It seems something is still missing. And I cannot find the highlighted id in either solution.xml or customizations.xml

Invalid Argument. : Microsoft.Crm.CrmException: Entity Display Collection Name for id: 5f69b9db-183c-418e-93d2-80ce68650db0, objectcolumn: LocalizedCollectionName and labelTypeCode: Entity not specified at Microsoft.Crm.Metadata.LocalizedLabelHelper.ValidateLabelCollectionContents(LabelCollection labelCollection, Guid objectId, String objectColumnName, LabelTypeCode labelTypeCode, String parameterName, ISqlExecutionContext context, Boolean throwIfCollectionIsNullOrEmpty) at Microsoft.Crm.Metadata.EntityService.ValidateEntityNameAndLabels(EntityCreateInfo entityInfo, MetadataHelper metadataHelper, ISqlExecutionContext sqlContext) at Microsoft.Crm.Metadata.EntityService.ValidateForCreate(EntityCreateInfo entityInfo, MetadataHelper metadataHelper, ExecutionContext context) at Microsoft.Crm.Metadata.EntityService.<>c__DisplayClass74_0.<CreateInternal>b__0() at Microsoft.Crm.SqlTelemetryHelper.LogSqlTimes(Action action, String operationName) at Microsoft.Crm.Metadata.EntityService.CreateInternal(EntityCreateInfo entityInfo, MetadataHelper metadataHelper, ExecutionContext context) at Microsoft.Crm.Metadata.EntityService.<>c__DisplayClass27_1.<CreateInternalHelper>b__3() at Microsoft.Crm.SqlTelemetryHelper.LogSqlTimes(Action action, String operationName) at Microsoft.Crm.Metadata.EntityService.CreateInternalHelper(EntityCreateInfo entityInfo, MetadataHelper metadataHelper, ExecutionContext context)

Was this reply helpful? Yes No
kevin.dynamics 10 on at

Like (0)

Report
Copy link

Link copied!

Finally got the solution imported by following the bellow approach:

1. check "include entity metadata" for the new entity that is added to the solution.

2. Manually remove the missing dependencies nodes in solution.xml (Thanks Ragnar Hilmarsson for the link)

After the initial solution is imported, the followed solution update doesn't report missing dependencies for that entity anymore. So step 2 is not needed.

Thanks for all your suggestions and help. Although it works now, this may be an issue that MS should address in the future release.

Was this reply helpful? Yes No
FU Microsoft 5 on at

Like (0)

Report
Copy link

Link copied!

Unfortunately, this workaround doesn't work for deployment via Azure DevOps.

Has anyone figured out the cause of this issue????

Was this reply helpful? Yes No