"Error code 80040203" (Invalid Argument) error occurs when attempting to import a solution into Dynamics 365

When attempting to import a solution in Dynamics 365, you encounter the following error:

"The import of solution: <Solution Name> failed.
Error Code 80040203."

NOTE: This error code is documented here with the following information:

Name: InvalidArgument
Hex: 80040203
Number: -2147220989
Invalid argument.

This error can be caused for several reasons. If your error dialog references the following type of object, review the rest of this article for a potential solution:

Type: Relationship
Name: bpf_<entity>_<publisher>_<BPF Name>

Download the Log File which when opened to the Components page will show:

ItemType: Entity Relationship
Name: bpf_<entity>_<publisher>_<BPF Name>
ErrorCode: 0x80040203
ErrorText: Attribute Display Name for id: <GUID>, objectcolumn: DisplayName and labelTypeCode: Attribute not specified

The Name of the Entity Relationship will be the concatenation of an Entity and a Business Process Flow (BPF). The Entity was previously removed from a BPF stage and replaced with a different Entity and then the BPF was updated while still Activated. The entity has been removed from the BPF but the relationship still exists in the schema so it is exported with the solution from the source. This relationship is causing the error displayed.

Microsoft is aware of this issue and is working on a change to remove this relationship after a delete then update.

There are two work arounds for this issue:

Option 1 - Update Solution File.

If you need to import the solution and cannot recreate the solution package then remove the relationship from the solution.

1. Unzip the solution
2. Edit the customization.xml
3. Search for the relationship mentioned in the error: bpf_<entity>_<publisher>_<BPF Name>
4. Delete all the XML for the EntityRelationship:
   
   <EntityRelationship Name="bpf_<entity>_<publisher>_<BPF Name>">
   ...
   </EntityRelationship>
5. Save the file
6. Zip the entire directory
7. Import the solution again.

Option 2 - Remove the relationship from the source and recreate your solution.

This is a long term resolution and will fix the issue for the next export of the solution.

1. Open the source organization.
2. Settings / Customizations / Customize the System
3. Select the Entity in the relationship:
   
   bpf_<entity>_<publisher>_<BPF Name>
4. Expand 1:N Relationships
5. Locate the relationship:
   
   bpf_<entity>_<publisher>_<BPF Name>
6. Select and delete the relationship.
7. Publish All Customizations
8. Export the solution and import it into the target.