Skip to main content

Notifications

Announcements

No record found.

Customer experience | Sales, Customer Insights,...
Suggested answer

Import failure because dependencies

Posted on by

Hi,

While importing solution in production, got below error.

The dependent component EntityRelationship (Id=contact_SharePointDocuments) does not exist.  Failure trying to associate it with SystemForm (Id=3eb0333c-255e-410b-900d-f851b8f8407c) as a dependency. Missing dependency lookup type = PrimaryNameLookup.

Is there any way to fix this?

Thanks

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Import failure because dependencies

    Hi,

    Please check whether you are selecting system form or not if yes then add the dependent like view another system from.

    this error would occur if that dependent component isn't in the solution and not in the target organization.

    Thanks,

    Arshad

    For interview preparation please go through the below link.

    https://juniorcrmblog.blogspot.com/2021/08/ms-dynamic-crm-interview-question-for-2.html 

    https://www.youtube.com/channel/UC3Pe9Y_2SxA9xAmTfuSWQaA/videos

  • Suggested answer
    Rektec Profile Picture
    Rektec 10 on at
    RE: Import failure because dependencies

    你好,我刚好遇到这个问题,已经解决了

    原因:出现这个错误的原因是你的开发环境联系实体开启了“文档管理”(解决方案>实体>通用信息),然后这个功能可能因为某种原因被关闭了。碰巧这个聪明的改变会导致你的错误。

    解决方法:首先需要在实体的通用选项中开启“文档管理”,添加文档实体的n:1关系(contact_sharepointdocuments),然后导入生产环境即可解决

  • Michael Mayo Profile Picture
    Michael Mayo 62 on at
    RE: Import failure because dependencies

    This is not a correct path to head down. Even without a sharepoint document integration at all, the "The dependent component EntityRelationship (Id=contact_SharePointDocuments) does not exist." error occurs and there is some underlying issue with solution transportation exists likely as a result of a solution coming from an org and exported previously (perhaps as much as from a month or two ago) and going into a newly created org. I suspect support may be familiar with this, but this is not an administrative mistake, it is a support issue.

  • Timothy Bohte Profile Picture
    Timothy Bohte 2 on at
    RE: Import failure because dependencies

    Follow the following instructions: docs.microsoft.com/.../enable-sharepoint-document-management-specific-entities

  • CRMQQ Profile Picture
    CRMQQ on at
    RE: Import failure because dependencies

    Thanks Timothy!

    Can you please tell me how can I enable SharePoint integration for contact in environment.

  • Suggested answer
    Nya Profile Picture
    Nya 29,056 on at
    RE: Import failure because dependencies

    Hi,

    It is recommended to follow this tutorial to remove the missing dependencies from your solution:

    Remove missing dependencies from solution XML with PowerShell - NETWORG Blog (thenetw.org)

  • Suggested answer
    Timothy Bohte Profile Picture
    Timothy Bohte 2 on at
    RE: Import failure because dependencies

    Hi,

    Please check if sharepoint integration for the contact entity is enabled in the production environment before importing the solution.

    Regards,

    Timothy 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans