Answered

Unmanaged Solution dependency on the Active solution with type 2

(1) Share

Report

Posted on by JustRhonda

225

When I run the Solution checker in my unmanaged dev environment, I have 2 Medium Issues that I do not understand how to resolve:

"The solution.xml for the solution xxx

contains an unmanaged dependency on the Active solution with type 2, schemaName ownerid, displayName Owner. A solution will fail to import in a target environment when missing dependencies on unmanaged components are present."

I have confirmed the Activity and Task table have required objects. What else can I try?

I'm running 2023 release wave 2 with Dynamics365 Customer Service

Categories:

Error handling

I have the same question (1)

All responses (3)

Answers (1)

JustRhonda 225 on at

Like (0)

Report
Copy link

Link copied!

Someone suggested I run the XRM Toolbox Solution Dependency Checker which shows No Missing Components. Am I chasing an error that isn't real?

Was this reply helpful? Yes No
Verified answer

JustRhonda 225 on at

Like (2)

Report
Copy link

Link copied!
Here is how I resolved my own issue:
After running the Solution checker and reviewing the errors. Go back to the exported solution zip file.
Open the Solution.xml (mine opens in a browser window)
My error message mentioned "ownerid" as being the field with a dependency so I did a find for 'ownerid' and it shows with the following matches: (Note, I find it confusing because there are many 'Missing Dependency' rows but I guess you only have to worry about the columns being referenced by the Solution checker)
The field is found in the "Knowledge Article Template" table/entity
In Power Apps, navigate to your solution and the Knowledge Article Template
Select Advanced > Add required objects
Select Ok from the confirmation panel
You will not see any details of what is added but it will say things are added.
Rerun Solution checker and the error is gone.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hey! I see there is an accepted answer for this already, but I had a similar issue and had a simpler fix. The issue is that there are relationships to another table not included in the solution. Another symptom of this issue is the automatic generation of a "DVTableSearch" object in your solution. Note that if it is a one-to-many relationship (i.e., the excluded table has a LookUp column referencing the table in your solution), the relationship still exists even though it isn't shown in the included table's data. If the table is important, be sure to include it in the solution! If not, I was able to resolve this error by going through each table in my solution, identifying any relationships to other (custom) tables outside the solution, and deleting the relationships. You may have to make changes to the excluded table such as making a column optional instead of required, removing columns in views, removing fields in forms, etc., to remove dependencies. Delete the DVTableSearch object after removing these relationships and you should be able to export/import without these errors.

Hope this helps someone!

Was this reply helpful? Yes No