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

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Problem with a solutio...
Customer experience | Sales, Customer Insights,...
Suggested Answer

Problem with a solution import dependency

(0) ShareShare
ReportReport
Posted on by Community Member

"

The dependent component EntityRelationship (Id=msdyn_product_knowledgearticle) does not exist.  Failure trying to associate it with SystemForm (Id=a640be62-63f6-4027-90d7-48c014a7c6f3) as a dependency. Missing dependency lookup type = PrimaryNameLookup.

I found this documentation for the error code: "There was an error calculating dependencies for this component. Missing component id : [GUID]" error occurs when importing a solution into Dynamics 365 (microsoft.com)

However, as you can see, the dependent component id is NOT a GUID.  Searching the solution.XML does NOT find the string "msdyn_product_knowledgearticle" anywhere.  It is an N-N relationship from some managed solution provided by microsoft.  Of the 3 resolutions given in the document

  1. I've tried a small solution with just the Product, Knoledge article and the relationship.  It won't take.
  2. The missing relationship is already in the larger solution.
  3. The larger solution does not present me with the option of removing components 

Something tells me this is an unusual situation -- perhaps that microsoft support has been looking at it for 2 days.

Has anyone ever see this -- or this pattern -- before?  Is there any way to determine the managed solution origin of the relationship?

I have the same question (0)
  • Suggested answer
    Nicholas Wanberg Profile Picture
    Nicholas Wanberg 2 on at
    Problem with a solution import dependency
    As I understand it, the primarynamelookup error means the table isn't missing, just a row on it. In my experience, it happens with cases where an object of the type that's recorded on that table isn't included in the solution but should be, yet it isn't registering correctly as a dependency for other checks, so it's not getting caught until later. In that's the case here, your knowledge article table exists in the target environment, but the knowledge article itself does not and should be included in the solution. 

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 183 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 121

#3
Gerardo Rentería García Profile Picture

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

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans