Can Dataverse tables be moved between environments?

[Future_Vision]

I have been building an app directly within PowerApps for Teams and utilizing Dataverse tables there. I've found working within Teams very limiting and have moved to the full editor in the browser. As a result I also started building in a new environment. I know I can connect to the Teams environment and access those tables I created but I'd prefer to simply move those tables over to my new environment. Is there an easy way to do this? I found some documentation on using the API but I'm not a programmer by trade and that seems like a daunting task. I'd probably be able to rebuild each and every table in the time it would take me to get that to work. 🙂

[GarethPrisk]

This isn't technically documented, but is possible.

1. Navigate to https://us.flow.microsoft.com
2. Select your environment (the name of the Team)
3. Select solutions on the left-hand menu
4. Create a solution
5. Add your tables
6. Export the solution as unmanaged
   • You have to navigate back from the screen where you add Tables
   • "Back to Solutions"
   • You can export from the Solution menu
7. Import the solution into your DataVerse environment

[Future_Vision]

Hmm. What I've found so far suggest using a solution but involve creating a duplicate of the schema first and then importing the data through a downloaded tool but you are saying this will do the same thing?

[GarethPrisk · Accepted solution]

Correct.

https://docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm

You'll be creating and using a standard unmanaged solution to move the components from one environment to another. The reality with a Dataverse for Teams app - however - is that you'll be using whatever prefix was randomly assigned. If you want your own prefix, then you'll need to recreate the components with your own solution prefix.

[Future_Vision]

With your original solution using Power Automate you can not change the prefix correct? Also, with that solution, do you 'Include all components" and " Include table metadata"?

[GarethPrisk]

The prefix of components cannot be changed in the UI, once set. Technically, you could export the solution, and then use tools or do some XML updates to correct them, and then import it as a new solution. This is finicky and I don't recommend it.

Yes @ include all components. Since you'll be moving the table in its entirety, you will want all of its components. Be mindful that the solution tool can, and will, bring in other tables/entities that you don't want (due to dependencies). Be sure to check your solution so it only includes the tables you created. Remove any system tables which may get added, unless you customized those as well.

[Future_Vision]

I understand this is beyond the original question but is the only way to create tables with a custom prefix is to create a solution and a publisher and build that tables in the solution? And will that table be available to other apps?

Hopefully I asked that correctly. Now that I am moving out of the restrictions of the PowerApps for Teams I'm just now getting to understand the plumbing behind the scenes.