Microsoft Dynamics 365 | Integration, Dataverse...

Error 0x80040216

(0) Share

Report

Posted on by KerriS

Can anyone assist with the following error? I have 3 instances (DEV,UAT,PROD) I am trying to deploy the solution to Production, however i am experiencing the below error. The solution imported successfully from DEV to UAT, this error is occurring when i try to deploy to the production instance.

The error code is 0x80040216 - There needs to be a one-to-one mapping between description and instance id. No matching ControlDescription found for the custom Control.

I have the same question (0)

All responses (9)

Answers (0)

LeoAlt 16,331 Moderator on at

Like (0)

Report

Hi partner,

Did you add all the components of the entity into your solution? According to the error message, it seems that you did not add the complete

components of the custom entity into the solution. I found some similar posts for your reference.

community.dynamics.com/.../error-0x80040216-during-data-import-to-dynamics-365-crm

community.dynamics.com/.../solution-import-failed---error-code-0x80040216

Hope it helps.

Best Regards,

Leo

Was this reply helpful? Yes No
RaviKashyap 55,410 Moderator on at

Like (0)

Report

Hi,

One way to trpubleshoot this issue is to move components from this solution to multiple small solution and then try to import these small ssolution and see which one failed. You can then investigate further on the failed components.

Was this reply helpful? Yes No
KerriS 5 on at

Like (0)

Report

Yes all components are added into the solution. Looking at the similar posts i am wondering if this relates to the editable grid. The error is directing me to an issue with the form with the error of one-to-one mapping between description and instance id. Will see if this resolves the error.

Many Thanks

Kerri

Was this reply helpful? Yes No
LeoAlt 16,331 Moderator on at

Like (0)

Report

Hi KerriS,

Thanks for your reply. Have you resolved your issue now? If our answers helped you, please mark the answer as verified to close the thread and help other users with similar issues.

Hava a nice day.

Best Regards,

Leo

Was this reply helpful? Yes No
KerriS 5 on at

Like (0)

Report

Hi Leo,

No this didn't actually resolve the issue. I have a support ticket with Microsoft so when they confirm the resolution i will update the post for users with similar issues.

Best Regards,

Kerri

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Even I had the same error few days ago. After some research I found out that there is a wikifixes page for the above-mentioned error. It has a link to an .exe file which after installation, rectifies the above-mentioned error. Try it and tell me whether it works for you, too.

Regards.

Was this reply helpful? Yes No
Julian Rickert 20 on at

Like (0)

Report

Running into a similiar issue. Have you resolved the issue? If yes, how did you resolve the problem?

Was this reply helpful? Yes No
Julian Rickert 20 on at

Like (0)

Report

Hi Ruskin, can you please provide a link to the wikifixes page you found?

Was this reply helpful? Yes No
Suggested answer

Andreas Volkmann on at

Like (0)

Report

In my case I was missing a solution action on the control description.

Adding solutionaction="Added" fixed the issue for me.

<controlDescription forControl="{1ac75918-44e8-6c83-2694-11cd0395e437}" solutionaction="Added">

Was this reply helpful? Yes No