Unanswered

Exporting/Upgrading a solution with dataverse tables in

(1) Share

Report

Posted on by EB-14031028-0

Hi all, pretty new to all things PowerApps and am planning on making an App that has a function allowing users to update/add a record to a dataverse table.

lets assume I have a solution in a dev environment with an App, multiple flows and connections, and a dataverse table, that I then export to a different environment as a managed solution. The app is then used for a period and records are added to the table.

If at a later date I make a change to the app in the dev environment, export it, and install it as an upgrade in the prod environment, does this overwrite the table in the prod environment and therefore get rid of any records in the existing table, therefore losing data? Is the answer to this question any different if instead of making an update to the app I change something about the table (e.g. add a new column), or if I do an update instead of a upgrade?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (2)

Verified answer

Michael E. Gernaey 53,325 Super User 2025 Season 2 on at

Like (1)

Report

Hi @EB-14031028-0

Change your app:

It will not delete your tables or data.

Adding a new column

Will not delete your data etc, however if you make this a required column that in fact has no data in it because data already exists it will be a problem.

If you are removing columns or adding columns and then shifting data, all of this can require literally moving your data and migrating.

It can in different cases, require you to create a whole new Table and migrate the data.

The level of changes you make dictate what will happen. But you should never lose the data, UNLESS you specifically remove the table, on purpose.

However, I must express my concern if you are going from Dev directly to Production. This would easily be answered (for your Sanity and for the sake of your Company) but having a Test environment, even if its just another Development environment that you only import managed solutions too.

Was this reply helpful? Yes No
Verified answer

Rajkumar_M 3,741 Super User 2025 Season 2 on at

Like (1)

Report

Data in Dataverse tables is not overwritten or deleted during solution updates or upgrades unless you explicitly remove the table or components.
Adding new columns or modifying the schema does not affect existing records.
Updates apply changes incrementally, while upgrades replace the solution entirely (potentially removing components).
Always test and back up data before deploying changes to production.

Best Practices to Avoid Data Loss:

✅ Use "Update" instead of "Upgrade" whenever possible.

✅ Exclude Dataverse Tables from the Solution if you are only updating the app or flows.

✅ Use Data Export as a backup before making table modifications.

✅ Avoid deleting columns unless absolutely necessary.

Thanks!

If my response has been helpful in resolving your issue, I kindly request that you consider clicking "Accept as solution" and "giving it a thumbs up" as a token of appreciation.

Was this reply helpful? Yes No