Unmanaged solution import failing due to phantom managed solution dependencies

(0) Share

Report

Posted on by sibonginkosinga

Hello,

I have recreated an unmanaged solution in my environment based on an existing managed solution. I included all the necessary components tables, columns, relationships, views, and forms; and ensured that the publisher prefixes and schema names match the original solution.

However, when I try to import this unmanaged solution into a new environment, the import fails. The system reports missing dependencies that point to the very components I am trying to import (for example, StockAllocated, Roles, and UsersAllocator).

I understand that managed solutions can create internal or hidden relationships that aren’t visible in the UI, but I’m not sure how to resolve this so that the unmanaged solution can be successfully imported into a new tenant.

What I’ve tried so far:

Created a new unmanaged solution and added all existing components
Verified that all publisher prefixes and schema names match the original managed solution.
Published all customizations before export.

Question:

Has anyone encountered similar issues with importing unmanaged solutions derived from managed solutions? Is there a way to bypass or clear these internal/phantom dependencies?

Thank you for any guidance.

Categories:

Power Apps component framework

Application Lifecycle Management (ALM)

Power Platform Build Tools

I have the same question (0)

All responses (3)

Answers (0)

Michael E. Gernaey 47,125 Super User 2025 Season 2 on at

Like (0)

Report

Unmanaged solution import failing due to phantom managed solution dependencies

HI @sibonginkosinga

Yes, I understood clearly what you said. But you have a solution that is dependent on something it expects to already be there. Not something that is in your solution two different things.

Was this reply helpful? Yes No
sibonginkosinga 2 on at

Like (0)

Report

Unmanaged solution import failing due to phantom managed solution dependencies

Hi @Michael E. Gernaey, all the dependencies that it is saying are missing are part of the solution I am trying to import. I recreated an unmanaged solution from the managed one in the source tenant. Most of the "missing dependencies" are the actual tables I am trying to get across to the new tenant.

Was this reply helpful? Yes No
Suggested answer

Michael E. Gernaey 47,125 Super User 2025 Season 2 on at

Like (0)

Report

Unmanaged solution import failing due to phantom managed solution dependencies

Hi @sibonginkosinga

No, I have not had that, but I would have to see the actual steps you took.

Remembering that just because you add the stuff doesn't mean there arent real dependencies.

And as an FYI, there should never be a "hidden" dependency if you have added all dependencies. It is certainly possible for a dependency to not have been added to a solution, but that doesn't... per se hide it, you just didn't add it (and by you I mean anyone).

Auto create Environment Variables for Canvas App connections... they do not automatically get put into the solution but they are still a dependency.

If something in the solution requires those things to already exist, then you need a base solution first, then your other parts.

So you would need 2 solutions to resolve the issue you are explaining.

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No