Notifications
Announcements
I am starting to build my first PowerApp in the web version (previous app was built in PowerApps for Teams a couple of years ago). Is there a way to build in a dev environment and deploy to production? These are the environment I currently have.
Take a look at the section on this page about Solutions. You have the right Environments for a Dev/Test/Production setup. What you need to learn is how to use Solutions to deploy your apps. Application lifecycle management (ALM) with Microsoft Power Platform - Power Platform | Microsoft Learn
Good stuff. I've been looking for a resource like this. I'll need to adapt it some. I am told that Trial environments haven't been set up internally because they have caused issues with security policies. But I am probably fine without the Trial (Test) environment. I should be able to build in development and test there and then deploy to production. Or maybe I need to leverage the Sandbox environment?
The developer plan has been improved to help support ALM. An individual user can now have up to 3 Developer environments. I would create another one of those for Test. Sandbox will work to, but Sandbox environments require capacity where Developer environments don't. I also wouldn't recommend Trial environments because they are time boxed.
Ah. Good to know. I will go that route then. Thanks!
Not sure if it is best to continue the discussion here or create a new question. I've been reading through the AML docs and specifically about solutions. When I create a PowerApp i should put everything for that app in the solution? I ask because I wouldn't want my Dataverse table from my Development or Test environments (Development Env 2) to overwrite the production tables. I am assuming I have control over what gets pushed to production.
I apologize if these are newbie questions. I am not a developer by trade. The answers to these questions might be obvious otherwise.
When you define a Dataverse table in a solution it only imports the schema of the table and not the actual data. So you can safely include dataverse tables in your solution. When you import into a new environment you will get the table, but it will have no data in it. For that you need to do something like run a flow to copy the data or use the Configuration tool to migrate the data.
Ok. This app I am building a is a V2 of an app I created in PowerApps for Teams a couple years ago. The data in the Dataverse tables for that app are still relevant and need to be prepopulated into this new app which I am building with a solution. How would I get that data over to this app? I imagine it would need to be imported into the development, test and production solutions if I want to have some seed data. And if I understand correctly, any changes I make to the Dataverse tables in development will remain in development and any change in test will remain in test and the same for production unless I overwrite the tables.
You've got three possibilities for migrating the data
1) Create a Dataflow in Power Apps
2) Create an instant Power Automate flow to read the one table and create records in the other. YOu can use the legacy Dataverse connector to connect to the environment you aren't in.
3) Use the Configuration migration tools see Configuration Migration tool - Power Platform | Microsoft Learn
You are correct that changes made after the migration will not be included in the next solution import except for schema changes to the table.
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.
In our never-ending quest to improve we are simplifying the forum hierarchy…
We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
WarrenBelz 717 Most Valuable Professional
Michael E. Gernaey 329 Super User 2025 Season 2
Power Platform 1919 268
