Power Platform Community Forum Thread Details

Hi everyone,

I’m running into an issue when trying to import a solution from our development environment to production.

During the import, I get an error about missing dependencies. The dependencies refer to system tables (for example tables with the msdyn_ prefix) that I did not create and do not use directly. I’m not sure where these tables came from or why they are now included in my solution.

What’s confusing is that until recently, I was able to import this solution to production without any problems. Nothing significant was intentionally changed in the solution structure.

I tried to add/install the missing components in the production environment, but I can’t find a way to do that. It seems like they are related to some system or first-party Microsoft package, but I don’t know how to install or enable it on production.

Has anyone encountered a similar issue with unexpected system-table dependencies when moving solutions between environments?

How can I identify the root cause and resolve this properly?

Any guidance would be greatly appreciated.

Thanks!

Categories:

Building Power Apps

Error handling

Governance & administering

Hi @CU23021339-0,

Please check the below thread if it solves your issue, else go through the below steps:
Solved: Missing dependency on pipeline import of solution

1) Open the “Missing dependencies” panel during import --> note the Applications / Managed Solutions listed. This view is designed to point to the exact missing app/solution and often provides an Install/Update action.
2) In Power Platform Admin Center --> Environments --> (Prod) --> Resources --> Dynamics 365 apps:

Install the missing app(s) or
Update the app(s) so DEV and PROD versions match (Sales, Customer Service, Omnichannel, etc.).

Then re‑import.

3) If you want to remove the dependency, find what’s pulling it in:

In the source solution, use Show dependencies at component level to see Used by / Uses and remove the references

(e.g., sitemap areas, forms, views that touched those msdyn tables).

Alternate approach:
Export the solution, inspect solution.xml --> <MissingDependencies>, and remove entries, then re‑pack and import.
Be cautious, this bypasses safety checks, only use when you fully understand the impact.

There is

References:
https://learn.microsoft.com/en-us/troubleshoot/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import

https://rishandigital.com/dynamics365/troubleshooting-solution-imports/

https://www.burgersandbytes.nl/blog/20250106-importerrordependency/

https://dev.to/nikhildynamicsce/dynamics-365-solution-import-error-missing-dependency-from-sales-app-how-i-resolved-it-20jo

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.