Microsoft Dynamics 365 | Integration, Dataverse...

Solution Import failing for PluginTypeExportKey is not found.

(2) Share

Report

Posted on by RA-12021357-0

First-time solution import went fine.

Removed all the plugin steps.

Now trying to reimport and facing this issue.

SDK Message Processing Steps import: FAILURE: A record for PluginType with hash value XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX for PluginTypeExportKey is not found. Please try again with correct value

Error code

8004023B

Any suggestion?

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Holly Huffman 6,538 Super User 2025 Season 2 on at

Like (0)

Report
This error typically occurs when the system cannot find a record for the PluginType with the specified hash value.

Apologies if you've tried these already, just thinking:

is the plugin assembly associated with the PluginType present in the target environment? If not, re-import the plugin assembly into the target environment before importing the solution.

could there be a mismatch between the PluginType in the source and target environments? validate the PluginType exists in the target environment and matches the one in the source environment.

any dependencies that might be causing the issue? verify all dependencies are present configured in the target environment.

all else fails - try cleaning up the target environment by removing any remnants of the previous import and then re-importing the solution

Was this reply helpful? Yes No
Suggested answer

CU14020600-0 2 on at

Like (0)

Report

Issue and Resolution Summary

I quickly discovered what was causing the issue. Sharing it here to help others avoid the same mistake.

Background:
I was using a dependent assembly package for the plugin assembly. The unpacked solution was checked into Git, and the build pipeline was repackaging it before deployment. However, the deployment was failing.

Cause of the Issue:
A required NuGet package from the unpacked solution was not syncing with Git from my local.

Solution:
I resolved the issue by updating my .gitignore file to include the specific NuGet package. After this change, everything worked as expected.

Alternative Approach:
This issue could also be resolved by configuring file mapping for the NuGet package in the build pipeline during the solution packaging process.

Thanks @Holly Huffman your first suggestion was insightful.

Was this reply helpful? Yes No