Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Apps - Microsoft Dataverse
Answered

Issue with exporting/ importing Dataverse tables originally created in Dynamics 365

(0) ShareShare
ReportReport
Posted on by 36

My company have recently brought me into a project which is upgrading their current CRM solution. Before joining the project the team had already start creating the tables (previously known as entities) via the Dynamics 365 classic interface as they originally planned to make a model driven app.

 

The approach has now changed so we will be using those same tables with a Canvas app but connecting to those tables via the Dataverse tables (the entities created in classic Dynamics are automatically created in Dataverse).

 

So now I have created a Solution in our Dev environment, in which I have created a Canvas app and added the existing Dataverse tables. However when I try to export/ import the solution to our Test environment I get the error:

 

"There are missing dependencies. Install the following solutions before installing this one: Active"
 
This is a very generic error message and I have tried to fix it by ensuring all the related tables have been added to the solution however I am suspecting that when the tables where created in Dynamics 365 classic interface it created extra component such as Views, Forms etc. and Power Apps is not liking this.
 
To prove my point I created a new Dataverse table directly within a Power Apps solution and it created no Views, Forms and I was able to export/ import across environments fine.
 
The issue is the project team have created a large number of tables and columns in Dynamics 365 classic and it will be a time consuming effort to recreate them in a Solution.
 
So to avoid them having to do that my question is; is there either a quick way of recreating those tables or adding them into the solution as fresh Dataverse tables without the additional components? (PS. I have already tried adding existing tables and then manually selecting only the columns and relationships but was still getting the error).
  • Smemmi Profile Picture
    36 on at
    Re: Issue with exporting/ importing Dataverse tables originally created in Dynamics 365

    Yes looks like there wasn't any easier way then to check the log file or solution.xml file and bring in the dependencies. Also the below link helped examine the dependant types:

    https://docs.microsoft.com/en-us/dynamics365/customer-engagement/web-api/dependency?view=dynamics-ce-odata-9

     Thanks for your help.

  • Verified answer
    MayankP Profile Picture
    462 on at
    Re: Issue with exporting/ importing Dataverse tables originally created in Dynamics 365

    you can use XRMToolbox tool "DependencyIdentifier" to identify all dependencies and make sure this will be included in the solution and this error will go away..

     

    https://github.com/Power-Maverick/DependencyIdentifier

     

     

    other option is to export solution zip and extract zip folder and examine xml file (solution.xml) and look at dependency section in there, that will also provide details on what components are missing from solution... 

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

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Leaderboard > Power Apps - Microsoft Dataverse

#1
mmbr1606 Profile Picture

mmbr1606 22 Super User 2025 Season 1

#2
stampcoin Profile Picture

stampcoin 17

#3
ankit_singhal Profile Picture

ankit_singhal 11 Super User 2025 Season 1

Overall leaderboard

Featured topics