web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Import failure because dependencies

(0) ShareShare
ReportReport
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

I have the same question (1)
  • Suggested answer
    Timothy Bohte Profile Picture
    44 on at

    Hi,

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

    Regards,

    Timothy 

  • Suggested answer
    Nya Profile Picture
    29,060 on at

    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)

  • CRMQQ Profile Picture
    on at

    Thanks Timothy!

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

  • Timothy Bohte Profile Picture
    44 on at

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

  • Michael Mayo Profile Picture
    13 on at

    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.

  • Suggested answer
    Rektec Profile Picture
    10 on at

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

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

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

  • Suggested answer
    Community Member Profile Picture
    on at

    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

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 170 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 61

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 52 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans