Power Apps

"Missing required unmanaged components"

(0) Share

Report

Posted on by kazut

I have two solutions in an environment, let's say solution A and B.

One table (let's call it X) in solution B has a column that looks up a table in solution A.

Now, when I try to export solution A, it recommends to add table X to the solution.

If I ignore it and export the solution, it cannot be imported because of this missing component.

If I add table X here, then the next time it suggests to add yet another table (let's call it Y), which looks up X.

It makes no sense to me. Solution B depends on solution A. Not vice versa. Why does this force me to include them and how can I avoid that?

Categories:

Building Power Apps

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Pstork1 69,244 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

The message you are seeing when you export is just a warning. If you know that Solution A is already installed in the destination environment you can just ignore the warning. It shouldn't prevent you from exporting and should pick up the table from the other solution in the destination environment.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
11manish 1,169 on at

Like (0)

Report
Copy link

Link copied!
You’re hitting one of the most confusing (and frustrating) behaviors in Microsoft Dataverse solution dependencies—but the system is actually behaving correctly based on how dependencies are calculated.

Let’s break it down clearly and fix it the right way.

You said:

Solution A → contains Table A

Solution B → contains Table X

Table X has a lookup to Table A

So logically:

B → depends on A

But Here’s the Catch

If anything inside Solution A references Table X, then dependency becomes:

A ↔ B (circular dependency)

This happens because:

Something in Solution A is referencing Table X (from Solution B)

Creating reverse dependency

How to Fix

Remove cross references from A → B

Or move shared components into a common core solution

Was this reply helpful? Yes No
kazut 15 on at

Like (0)

Report
Copy link

Link copied!

I cannot see any reply button to reply to the individual responses sorry.

@11manish there is no referencing from Solution A to Solution B. I know when creating a lookup column, the dependencies can be found on both tables, which I guess is the reason. It seems pretty ridiculous to me. I am not sure if it is possible to make it a one way dependency.

@Pstork1, yes it is a warning but when importing the exported file to another environment it is rejected because the export is missing table X.

So I ended up with adding table X to solution A, then further added table Y which depends on X, then Z...... repeat adding "missing" tables like six or seven times until I include literally ALL custom tables I have in the environment that have nothing to do with solution A. Truly ridiculous. My solution A need only 5 tables. Now it includes like 27 tables.

Was this reply helpful? Yes No
Pstork1 69,244 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Yes, the table needs to exist in the destination environment before you import the solution that depends on it. So if Table X in Solution B depends on a Table in Solution A then Solution A must be imported into the destination environment before you import Solution B. If its done in that order everything should be fine. It sounds like you have Tables in both solutions that depend on the other solution. If that's the case then they should ALL be in one Solution. Otherwise you'll run into interlocking dependencies.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No