Solution import fails due to pre-existing entity's and objects

(0) Share

Report

Posted on by Community Member

Ok I'm really interested to find out whats going on with this one. I've been thru the entire internet. (no really ;) ). Basically we are creating upgrade packages for some solutions and these new packages contain exactly the same attributes as the pre-existing packages. But they fail, either using maintain or overwrite customizations.

It flags an error, on one attribute, that the optionset schema name is not unique. When you remove that attribute, it then simply fails with no error messages (getting to the String Maps part of the process, and then not carrying on any further.)

So, I can rule out that the schema names are different, or that the attribute types are different (they are exactly the same in both the original solution and the update solution)

The only other thing to note, is that the attributes it's potentially trying to overwrite, (or not as the case maybe when using maintain customizations) do contain data.

All the solutions are managed, any thoughts are appreciated!

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Gus Gonzalez 27,113 on at

Like (0)

Report

Can you rename the attribute inside the customizations.xml and try to import again?

Was this reply helpful? Yes No
Waqar Sohail on at

Like (0)

Report

Hi, Please try to remove the attributes Xml of entity from customizations.xml. Aslo remove OOB tabs, Relationship, forms from the customizations.xml.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (1)

Report

The Root cause –an Attribute has been deleted then recreated in source environment. When recreated it got different schema name (Uppercase letters) but same logical name as the one deleted. In short, Schema names are case sensitive.

Resolution – Compare the schema name before you start importing customization.

If any attribute is there in the target but not in the source then check and remove these types of fields.

How to compare ? simply you can use one of available for free Metadata Browsers

Was this reply helpful? Yes No
Suggested answer

Hosk on at

Like (1)

Report

I have seen this scenario many times and it's usually caused by someone deleting a field and recreating a field with the same name but a different type.

What happens when they try to import this, CRM can't overwrite the field because it's a different type, so it tries to create the new field (but with the same schema name) and fails because it already exists.

You need to narrow down the entity and then compare the fields to see if any field types have changed between environments

Was this reply helpful? Yes No
Mohammed Fakhri 402 on at

Like (0)

Report

Hi Ben, I facing the same issue in Dynamics 365 Online. How do i resolve this. since we don't want to lose data in the prod attribute.

Was this reply helpful? Yes No