Unanswered

Solution check meta-include-missingunmanageddependencies

(0) Share

Report

Posted on by mightykoala59

Hi,

I'd be really grateful for any help. I have a solution in an unmanaged environment which I am running the solution checker on. I have 8 cloud flows in the solution, all referencing a table that's in the same environment but not in this solution - it's an error log table for when a cloud flow fails. For each flow I am getting a medium error:

The solution.xml for the solution XXXXX contains an unmanaged dependency on the Active solution with type 1, schemaName XXXX, displayName XXXXX. A solution will fail to import in a target environment when missing dependencies on unmanaged components are present.

How can I resolve this error? The same error appeared in previous solution.xml files but never flagged in the solution checker. I'd be appreciate of any help. When adding an empty error log table within the solution to see, the errors change to the same error but referencing all the other tables that are within the flows and solution.

Categories:

Governance & administering

I have the same question (0)

All responses (2)

Answers (0)

bopit_pax8 on at

Like (0)

Report

I also have this same problem. No dependency mentioned on solution checker either!
meta-include-missingunmanageddependencies

Details Issue
The solution.xml for the solution Asset Management Training contains an unmanaged dependency on the Active solution with type 1, schemaName xxxx_assetallocationprocess, displayName Asset Allocation Process. A solution will fail to import in a target environment when missing dependencies on unmanaged components are present.

How to fix Add or Remove references to any reported unmanaged dependencies not included within the solution.
Ha check the the complete Guide!

Location Unspecified

Was this reply helpful? Yes No
Tyler Olson Microsoft Employee on at

Like (0)

Report

Hello @mightykoala59 and @beno_pax8,

This was a newer rule introduced to Solution Checker that helps identify when you have unmanaged dependencies tied to the 'Active' solution in your solution.xml file. When this occurs, the solution may fail to import if the missing unmanaged dependencies don't already exist in the target environment. Unmanaged dependencies tied to the Active solution are generally environment specific - so any identified components meeting these criteria should be included in the solution to avoid issues with downstream imports. Once the missing component dependencies are added to the solution, it can be exported and then imported to the destination target without issue. The Solution checker rule should also no longer raise a violation for those components that were added to the solution.

I will note that it looks like when this rule rolled out that the documentation link was incorrect. If you were not directed to the following page, then please find the correct documentation link here: Missing dependencies during solution import in Power Apps - Power Apps | Microsoft Learn

I hope this helps better understand the rule and its' goal to help avoid issues with downstream solution imports.

Warm Regards,
Tyler

Was this reply helpful? Yes No