Error when importing solution - EntityId is null

(0) Share

Report

Posted on by HFG

522

Hi all,

I'm trying to import a solution to our Test environment and I get the following message:

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

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

Does any one know what this means and how to solve it? I also have the GUID of the entity, but don't know how to find out which entity it is referring to.

In case it is relevant, in a previous import some columns had been removed in the DEV environment. They have now been readded in the DEV environment as we realised that they should be kept to avoid data loss. The columns have been readded with the same technical name and the relationships have been given the same names.

Thanks in advance for any help.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Mira Ghaly 11,415 Moderator on at

Like (1)

Report
Copy link

Link copied!

@HFG

Can you make sure that the same fields does not exist on the target environment , if they exist on the target environment please delete them and try to re-import the solution!

Was this reply helpful? Yes No
HFG 522 on at

Like (0)

Report
Copy link

Link copied!

Hi Mira,

Thanks for your reply. Can you tell me what this error message means?

There have been a lot of changes since the last time the solution was deployed so I'm really guessing that it could be linked to this but it could be anything really. If I understood the message a bit more I may be able to identify which change the problem is linked to.

Thanks

Was this reply helpful? Yes No
Verified answer

HFG 522 on at

Like (1)

Report
Copy link

Link copied!

It turns out the columns I mentioned had nothing to do with the problem. We imported the solution manually (before we were doing it through DevOps) and were able to get the logs which told us exactly which relationship/columns were causing the problems. There were LookUp columns and there was no obvious reason that they were blocking the deployment. After deleting the columns the import worked. We then readded them as before and the import worked. Strange!

Was this reply helpful? Yes No