Error importing managed solution: Attribute Display Name for id: xxxxxxx, objectcolumn: DisplayName and labelTypeCode: Attribute not specified

(0) Share

Report

Posted on by jatcube

508

Hi guys,

I've developed a model-driven solution, where the previous import was successful, but had to change the display names of some tables and form layouts. Now, I'm getting the below error code and exception message. I have numerous relationships defined as well with business rules and process flow all included in the solution.

Error code
80040203
Exception message
Attribute Display Name for id: xxxxxxxx, objectcolumn: DisplayName and labelTypeCode: Attribute not specified

The app works fine in dev environment, but can't import it as a managed solution into test. Every time I try to import the solution (same managed version) the id keeps changing and can't find any attributes with the id's specified anywhere.

I think some controls on some of the forms may reference something that's not actually there anymore, but isn't throwing any errors anywhere when using the app in dev.

Any ideas how to narrow down what the issue may be?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (1)

Gowri Halan 262 on at

Like (0)

Report

@jatcube Did you check this https://docs.microsoft.com/en-US/troubleshoot/dynamics-365/sales/error-code-80040203-invalid-argument-error ?

Was this reply helpful? Yes No
jatcube 508 on at

Like (1)

Report

@gowrihalan04 thanks for the suggestion, I did look at that article and the error log but couldn't find anything meaningful in there. Maybe I need to set aside an hour to properly go through it though.. I'll report back with any findings. Thanks again

Was this reply helpful? Yes No
Verified answer

jatcube 508 on at

Like (3)

Report
Managed to find a solution, and it's not what you think..

It turns out a residual business process flow that I had deleted many iterations ago using the modern UI somehow lingered around, only to activate with this export somehow and wreak havoc. Needless to say, it was nowhere to be found, since it was deleted.

However, Error code 80040203 Invalid Argument error - Dynamics 365 Sales | Microsoft Docs did give me the idea to go into the legacy admin center and take a look. Surprisingly, I found an orphan BPF I thought I had long deleted.. So I deleted it again. This time, for good.

Unfortunately, this didn't not solve the issue since this BPF was in no way connected to anything in my solution. The real issue is still unbeknownst to me, but thought since legacy interface has helped me out once, it might help me out again.

And indeed, editing the model-driven app in the classic interface - removing the only connected business process flow and adding it back, save and republish repaired my solution. Why? Maybe someone more skilled in D365 can answer that question.

So, the real solution here is really this:
don't expect error messages to tell you where the problem is, instead use them to guide you towards the solution

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

I did the same but the issue still seems not to be resolved "editing the model-driven app in the classic interface - removing the only connected business process flow and adding it back, save and republish repaired my solution."

Was this reply helpful? Yes No
JW-29040828-0 2 on at

Like (0)

Report

I encountered the same issue when importing a managed solution. The id in the error message also changed every time we imported the solution. This was what we saw in the logs after manually importing the solution and downloading the logs:

<Row ss:AutoFitHeight="0" type="Entity Relationships">

<Cell ss:StyleID="s137" name="Time">

<Data ss:Type="String">09:00:33.00</Data>

</Cell>

<Cell ss:StyleID="s137" name="ItemType">

<Data ss:Type="String">Entity Relationships</Data>

</Cell>

<Cell ss:StyleID="s137" name="Id">

<Data ss:Type="String"/>

</Cell>

<Cell ss:StyleID="s137" name="Name">

<Data ss:Type="String">Table1_Table2_Relationship</Data>

</Cell>

<Cell ss:StyleID="s137" name="LocalizedName">

<Data ss:Type="String"/>

</Cell>

<Cell ss:StyleID="s137" name="OriginalName">

<Data ss:Type="String"/>

</Cell>

<Cell ss:StyleID="s137" name="Description">

<Data ss:Type="String"/>

</Cell>

<Cell ss:StyleID="s137" name="Status">

<Data ss:Type="String">Failure</Data>

</Cell>

<Cell ss:StyleID="s137" name="ErrorCode">

<Data ss:Type="String">0x80040203</Data>

</Cell>

<Cell ss:StyleID="s137" name="ErrorText">

<Data ss:Type="String">Attribute Display Name for id: xxx-xxx-xxx, objectcolumn: DisplayName and labelTypeCode: Attribute not specified</Data>

Turns out it was because there was a lookup field on Table2, which looks for a record on Table1. The relationship (Table1_Table2_Relationship) on Table1 was included in the managed solution, but the new lookup field in Table2's entity.xml was left out by accident. We added the Lookup field back into the managed solution and the problem was resolved.

Was this reply helpful? Yes No