Microsoft Dynamics 365 | Integration, Dataverse...

Custom Entity Import Failed Error 0x80040203 Attributeid is Null

(0) Share

Report

Posted on by JKN303

I have created a custom entity that links existing employees with projects they completed when they were not with our company (outside experience). These projects contain (among other fields) a lookup for employee and a subrid for a many-to-many relationship with another entity called markets (the classification of the project as many projects fall into many categories - this is used also with our historical projects entity as well as others). This solution works without incident on our test environment but throws an error when I import to production. The error appears to be on the project to market relationship with the notes "Attributeid is null."

Error log below. Has anyone run into this before? Thanks

All responses (7)

Answers (0)

Christian K 138 on at

Like (1)

Report

RE: Custom Entity Import Failed Error 0x80040203 Attributeid is Null

Yes, the above solution is correct! worked for me as well that way at the time
Suggested answer

Santiago PC 5 on at

Like (1)

Report

RE: Custom Entity Import Failed Error 0x80040203 Attributeid is Null

Hi,

I experimented a similar issue.

In my case I tried to import a solution from the UAT environment to the Golden (both sandbox environments) with few fields in different tables which were related to the table "Users" (Systemuser).

When I imported the solution, the error message Jess mentioned appeared.

The issue was that the same fields with the same names (both tags and logical names) have been imported before so the relationships of those fields did not match because they were related to the table "Workers", so the system interpretates that as an error.

The solution was to delete the fields and their relationships and dependencies on the Golden environment and reimport the new fields from the UAT.

Hope this solution can help.

Santi
Suggested answer

Kaida Theen 10 on at

Like (0)

Report

RE: Custom Entity Import Failed Error 0x80040203 Attributeid is Null

Hi,

I had the same problem and the solution was that the same Field (-Relationship) already existed in the Destination system (Test System). Maybe created by accident - I don't know

I checked if there was data in the field and if it was used somewhere. It was not in use and did not have dependencies. So I deleted the field on the destination and afterwards I was able to import the solution successfully.
Christian K 138 on at

Like (0)

Report

RE: Custom Entity Import Failed Error 0x80040203 Attributeid is Null

Experiencing the same problem. Any additional insights on this??
HFG 20 on at

Like (0)

Report

RE: Custom Entity Import Failed Error 0x80040203 Attributeid is Null

Hi,

Did you find an answer to this? I am receiving the message below when I try to import:

Microsoft.Crm.CrmException: AttributeId is null ---> Microsoft.Crm.CrmException: AttributeId is null

at Microsoft.Crm.Metadata.RelationshipConditionCreateAction.Validate()

Thanks
JKN303 5 on at

Like (0)

Report

RE: Custom Entity Import Failed Error 0x80040203 Attributeid is Null

Thank you so much for your answer, Nya, but I'm still confused. I'm not trying to bring data between the two instances. All I'm trying to do is port customizations between them - no data is involved. The data sets are completely separate between the two environments and we want to keep them that way.

Any other thoughts?
Nya Ng 185 on at

Like (0)

Report
RE: Custom Entity Import Failed Error 0x80040203 Attributeid is Null

Hi Jess,

For the relationships between the custom entities are a bit inexplicit, I cannot fully simulate the problem you are experiencing.

The Data Import ++ tool in XrmToolBox is recommended to import the records of the entity since it can show more detailed reasons for import failures.

Also, the Configuration Migration tool is recommended for importing data across environments.

Connect to Environment A.

Export data from it.

Connect to Environment B and import the data into it.

Ensure that the Entity structure of the two environments is the same, so you can quickly synchronize the data between the two sides.

If this helped you, I'd appreciate it if you'd mark this as a Verified Answer, which may in turn help others as well.

Best Regards,

Nya