Unanswered

Create a Dataverse database using a SQL create script (or other script)

(1) Share

Report

Posted on by nolanfromcanada

I know Microsoft wants us to use Dataverse as the back-end for Power Apps (I want to too).

In a previous life, as a developer, I would design databases using a schema editor and generate SQL create scripts that would allow me to bring up and tear down MySQL databases very quickly. I could also add dummy data easily by just running the script.

Is there an equivalent design workflow for Dataverse. I just find using GUI to build databases with many tables and columns very challenging. I much prefer working in a schema editor or a text-based script.

What about version control on database designs? How is that handled?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report

Hi @nolanfromcanada,

I am afraid there is no such thing. You can use the Web API or SDKs to programmatically create metadata, or even go as far as to write your own schema editor, but the metadata is much more in depth and complex compared to standard T-SQL DDL. I don't think the end result would be any faster than the UI for this type of thing, especially when you consider scripts are more prone to errors.

With regards to managing in source control, you can use the Solution Packager to Unpack a solution into its XML format which is source control friendly. Have a look at the reference below at the tools available. There are also build tools provided by Microsoft for Azure DevOps and Github Actions that use these tools under the hood to Automate build and deployment processes.

https://docs.microsoft.com/en-us/power-platform/alm/configure-and-deploy-tools

https://docs.microsoft.com/en-us/power-platform/alm/devops-build-tools

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
Fubar 8,338 Super User 2025 Season 2 on at

Like (1)

Report

Putting all your changes in Solution files is how you facilitate the movement and setup of new environments etc.

You could possibly look at XrmToolBox.com there are a couple of plugins: MS Sql To CRM Import, Attributes Factory, Attributes Creator.

You do also need to be mindful that there are a lot of out-of-the-box fields on pre-existing entities and try not to re-create ones that already exist e.g. multiple fields with the same Display Name are allowed (unique schema but non-unique display name) and the users and often your general usage is Display Name,

Was this reply helpful? Yes No
court2 5 on at

Like (1)

Report

I'm struggling with this huge inefficency, as well, as I contemplate building a database in dataverse. The workflow of 'create one field, hit save, wait 7 seconds, repeat' is not conducive to maintaining enthusiasm or sanity.

I think dataverse can now upload from more sources--maybe even SQL. That won't help me with only Excel and Access (I know there are connectors for these, too, but Excel / csv seems to be pretty fragile based on my starting point.)

Would love any thoughts / updates on best practices for getting a whole schema into Dataverse quickly. Anything but the current 'workflow'!

Was this reply helpful? Yes No
KrishanG 6 on at

Like (2)

Report

I find creating tables schema extremely painful using this ui editor in Dataverse. For people who have been doing lots of back end development the UI actually constrains you and slows you down.

I disagree with what you say, the scripting method will be faster for a developer who already has table schema close to what needs to be transformed too, and all one needs to do is add or subtract any fields not required and execute the script which would create the entire table. Hope this functionality of writing T-SQL will be brought into PowerApps.

Was this reply helpful? Yes No