web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Error with solution im...
Power Apps
Suggested Answer

Error with solution import

(1) ShareShare
ReportReport
Posted on by 6

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?

png.png
I have the same question (0)
  • Suggested answer
    Assisted by AI
    oyepanky Profile Picture
    537 on at

    Hi,

    This error happens because your solution now depends on a Microsoft-managed solution (tables with msdyn_ prefix like msdyn_DealClosingAgent).

    These tables come from a Dynamics 365 app (Sales / Customer Insights / etc.) installed in your DEV environment but not installed in Production.

    That’s why the import fails with missing dependencies.

    Sultions
    1 (Recommended):

    • Install the same Dynamics 365 app in Production.
    • Go to Power Platform Admin Center
    • Open Production environment
    • Install the missing Dynamics 365 app
    • Retry import

    Solution 2:

    • If you don’t actually use those tables:
    • Check Account/Contact customizations
    • Remove any fields/relationships referencing msdyn tables
    • Re-export the solution
    • Import again  

    Why This Started Suddenly

    Most likely:

    • Someone customized Account or Contact
    • Or added a field/relationship that references that managed solution
    • Even indirect references create dependencies.

    You cannot manually create those msdyn tables — they belong to a Microsoft managed solution.

    If you share which tables are in your solution, I can guide you more specifically.


    24/7 Power Platform Support - Click Here
    Best regards,
    Pankaj Jangid (OyePanky)
    Power Platform Developer
    YouTube: https://www.youtube.com/@oyepanky
    Website: https://www.dialforit.com

  • SharonGr Profile Picture
    11 on at
     
    Yes, we have encountered this multiple times :)
    MS pushes out-of-box solutions to our environments which may lead to such dependency. Your solution may not have these tables, but your solution could have tables that depend on these new OOB tables - in this case, as seen in your snap Account and Contact table need the 'SCA Engage agent Result'
     
    What you need to do:
    1. Find the solution which is causing the issue - in this case the error gives you the table name - if you are not sure which solution is missing, go to Default solution -> search for this table -> Advanced -> See solution layers
    2. Verify that this solution from Microsoft is installed in all your environments
     
    In this case, it's most likely that the solution has been installed in your Dev and UAT and is likely missing in your Prod.
    Please check if all your environments are on the same Version
    And raise a MS ticket asking them to push the missing solution to your Production (usually done during off business hours)
     
    If you want to dig deep, you can also check the 'Solution History' of your Dev/UAT checking when was this solution pushed to your sandbox environment - sometimes these are displayed there - 
     
    And yes, this is a common issue where we have had solutions in our Dev and UAT but not Production because Production was 'missed' in the update cycle.
     
    Hope it helps 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Vish WR Profile Picture

Vish WR 421

#2
Valantis Profile Picture

Valantis 405

#3
timl Profile Picture

timl 337 Super User 2026 Season 1

Last 30 days Overall leaderboard