cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
emoii
Resolver I
Resolver I

PowerApps in production and in test [release management]

Hi all

 

We sucesfully launched our first app in production, and as it was the first, we also created and tested it in our production environment. The App is connected to 4 SPO lists in our production tenant.

 

Now, we know that we will further develope on this app, and we want it done in our test tenant. What is the best approach to achieve this.

 

What I tried was to replicate/migrate the 4 SPO lists to test. This went fine.

 

Then I did a export of the app, did a Import in test, this also went fine. But there are stil references to the lists in the other tenant. 

 

What I am asking is, what is the best approach to move a app to another envirnonment or a test tenant environment, further develope on it, test it, and then release/delpoy it to production again, and update the current app in production.

 

Is the best approach to stay in same environment, have multiple copies of the app one for Dev, one for Test, etc., and have multiple copies of the lists in production tenant also?

 

I am missing some guidelines in how the release management is best done with PowerApps.

1 ACCEPTED SOLUTION

Accepted Solutions
Mike2500
Super User
Super User

PowerApps was designed as an end user tool, and as such does not have rich support for typical develop wish list items like (good) version control, support for easily publishing among different environments, or support for easily changing out connection strings or credentials.

 

So, if you export and import an app, it will still have connections set to the original environment. To correct this, view the data connections, and delete them. Then, recreate them, pointing to the new sources, but ensure the names are the same. When you delete the source, all the controls on all forms will show red errors messages, as expected. Once the data sources are recreated with the same names, then all the errors should go away. Of course, the fields, data types, etc., all need to match between the environments.

 

Given the above, to update an app:

 

  1. make changes to the dev version
  2. export
  3. import to prod
  4. delete data sources
  5. recreate data sources
  6. test*
  7. publish

Note, the test phase isn't going to be a true test, as the preview experience in the designer has a few differences from how the the published version of the app will behave. So, in this sense, the can't actually be fully tested prior to being put into prod. Second, it goes without saying that making changes to the app in the prod environment as described above is a violation of very basic best practices for  managing apps. But that's the situation we're in.

View solution in original post

2 REPLIES 2
Mike2500
Super User
Super User

PowerApps was designed as an end user tool, and as such does not have rich support for typical develop wish list items like (good) version control, support for easily publishing among different environments, or support for easily changing out connection strings or credentials.

 

So, if you export and import an app, it will still have connections set to the original environment. To correct this, view the data connections, and delete them. Then, recreate them, pointing to the new sources, but ensure the names are the same. When you delete the source, all the controls on all forms will show red errors messages, as expected. Once the data sources are recreated with the same names, then all the errors should go away. Of course, the fields, data types, etc., all need to match between the environments.

 

Given the above, to update an app:

 

  1. make changes to the dev version
  2. export
  3. import to prod
  4. delete data sources
  5. recreate data sources
  6. test*
  7. publish

Note, the test phase isn't going to be a true test, as the preview experience in the designer has a few differences from how the the published version of the app will behave. So, in this sense, the can't actually be fully tested prior to being put into prod. Second, it goes without saying that making changes to the app in the prod environment as described above is a violation of very basic best practices for  managing apps. But that's the situation we're in.

Thanks.

 

That is not optimal, hope they will implement an easier way to do it. 

Helpful resources

Announcements
PA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.

PA.JPG

New Release Planning Portal (Preview)

Check out our new release planning portal, an interactive way to plan and prepare for upcoming features in Power Platform.

Top Solution Authors
Top Kudoed Authors
Users online (2,449)