cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Smemmi
Frequent Visitor

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

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).
1 ACCEPTED SOLUTION

Accepted Solutions
MayankP
Responsive Resident
Responsive Resident

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... 

View solution in original post

2 REPLIES 2
MayankP
Responsive Resident
Responsive Resident

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... 

Smemmi
Frequent Visitor

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...

 Thanks for your help.

Helpful resources

Announcements
Power Platform Call June 2022 768x460.png

Power Platform Community Call

Join us for the next call on August 17, 2022 at 8am PDT.

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Users online (4,270)