Issues importing managed solution

(0) Share

Report

Posted on by Marx2020

175

Hi,

Dynamics 365 CE 9.x

I have the typical 3 environments - Dev, UAT, Production. UAT and Production are Managed solutions.

I'm having trouble importing a managed package from Dev, as it wants to overwrite a (what I think is OOB) relationship: contact_parent_contact. The relationship is unmanaged within the UAT managed solution (for reasons I don't understand- I inherited these environments), and the relationship is identical in both environments. UAT Import is failing because of this (can't import managed over the top of an unmanaged relationship - will cause solution layer issues).

What's the tidiest way of remedying this? I really want to avoid uninstalling the UAT solution if I can....

thanks,

Steve

I have the same question (0)

All responses (11)

Answers (1)

Suggested answer

Jean Joel Kakou on at

Like (0)

Report

Hello Marx2020,

thank you for your post.

This relationship is coming from the org chart enable on the organization.

When using the org chart, the hierarchy settings will be auto-enabled if they weren't enabled before. A relationship with schema name contact_parent_contact will be created with the parent attribute schema name parent_contactid. If you wish to use a different relationship for the org chart, please contact your admin to create a new hierarchical relationship

You can find it here: Maintain an external org chart (Dynamics 365 Sales) | Microsoft Docs

Mitigation for contact_parent_contact issue:

1.Create the new account/company on the target org.

2.Open the account/company created and browse the Organization chart which will create field and relationship.

After you can try to import your solution on the target.

Was this reply helpful? Yes No
Marx2020 175 on at

Like (0)

Report

Hi Jean Joel,

Thanks for your response. Is an alternative to remove the relationship from my unmanaged solution before I export? Am I correct in assuming that the import/upgrade process will just ignore the existing relationship in the target (i.e. it will not remove it)?

cheers,

Steve.

Was this reply helpful? Yes No
Verified answer

Jean Joel Kakou on at

Like (0)

Report
Hello Steve,

I understand, the only way would be to remove the relationship on the solution on the source.

If the contact_parent_contact / parent_contactid are unmanaged on the target org:

You will have to remove the contact_parent_contact relationship and parent_contactid attribute from customizations.xml of solution managed and reimport the solution to the target

Extract the solution zip, open customizations.xml, remove the contact_parent_contact highlighted node

Zip the solution and import and upgrade again.

Was this reply helpful? Yes No
Jean Joel Kakou on at

Like (0)

Report

Hello Steve,

In Addition, I dont think it is a suitable solution for a long run because you will always do that when you will want to import your solution.

The unmanaged component on the target will always throw an error if you are importing your solution managed.

Could you please paste the exact error message that you have? I will update if you will have to raise a ticket for follow up on the issue?

Thank you

Was this reply helpful? Yes No
Marx2020 175 on at

Like (0)

Report

Hi Jean Joel,

I removed the relationship and entity from the upgrade package and it upgrade successfully. Interestingly, I have another problem which suggests that the (existing) relationship in UAT is the issue. Would it work to delete the relationship and field from the default solution in UAT and reimport a full upgrade from Dev?

Cheers,

Steve.

Was this reply helpful? Yes No
Marx2020 175 on at

Like (0)

Report

here's the error message:

A managed solution cannot overwrite the Relationship component 'contact_parent_contact' with Id=d43f93ee-867b-407a-938a-441786eb1eff which has an unmanaged base instance. The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged Relationship component on the target system, and now a managed solution from the same publisher is trying to install that same Relationship component as managed. This will cause an invalid layering of solutions on the target system and is not allowed.

Was this reply helpful? Yes No
Jetj25 534 on at

Like (0)

Report

We have the same problem today

Was this reply helpful? Yes No
Jean Joel Kakou on at

Like (0)

Report

Yeah this is the issue. I believe that you can use the temporary solution and create a ticket for follow up.

Was this reply helpful? Yes No
Marx2020 175 on at

Like (0)

Report

The alternate approach above also worked.

Was this reply helpful? Yes No
M.Nauman 5 on at

Like (0)

Report

Hi,

Has anyone solved this issue apart from removing the relation from customizations.xml?

Best

Nauman

Was this reply helpful? Yes No