You’re offline. This is a read only version of the page.
35
I made a Power App with a SharePoint site and provided this in a dev environment. I want to provide this is in a test and production environment as well, but I was wondering what about the SharePoint site? Do I need to make three seperated sites or what's the best practice for this?
as to SharePoint and ALM: I use one and the same SharePoint site, but create each time 3 seperate instances of Libraries or Lists (DEV/TEST/PROD). As to site columns or content types, these are in my use cases manageable without seperate ALM environments
Yes, that's what you'll have to do. There are third party tools for Application Lifecycle Management with SharePoint Online itself you could use.
Alternatively, you could use Dataverse. If you make changes to Dataverse tables, these schema changes will be applied to Test and Prod environments as part of the solution import process without your manually having to update them.
Hello @joe_hannes_col, thanks for your reply.
So if I make changes in a list (like a new column or rename a column) in my dev environment, I have to keep in mind what changes I need to make in my other SharePoint sites (like I manually need to add or edit the lists and and keep in mind what changes I need to make in the other environments as well)? It's like double work...
Hello @AH92,
Yes, the best practice is to create separate SharePoint Sites and lists for Dev, test and prod. You can use environment variables to connect to different sites and lists in your different environments without having to "hard-code" the different sites into your apps and flows: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables#create-an-environment-variable-in-a-solution
#1
Michael E. Gernaey
9
Super User 2025 Season 1
#2
bscarlavai33
5
Super User 2025 Season 1
#3
getsplash
2
Share
Report
All responses (
Answers (
