Power Apps Development Process

[ghdunn]

Hi,

Could anyone point me to some advice or references covering a development best practice for Model Driven Apps with Single App licence.  Forgive me if  some of his sound amateurish but I am relatively new to developing in the cloud.

As I say, we are subscribing to Power Apps single app licence. If I publish version 1.0 and then save but don't publish v1.1, then do v1.0 and v1.1 both still point at the same underlying database? If I carry out changes to the db schema, do those changes wait until the publish event to propagate?  What happens if I add data through the v1.1 UI before I have published?

Am I able to have an instance of the app ui AND database in Development/UAT (so effectively 2 environments) and then migrate over the schema and UI changes, or do I simply keep a log of my schema changes and replicated them in Prod.

Thanks,

Ged

[HSheild · Accepted solution]

Hi @ghdunn

A good reference in regards to solutions and propagating configuration (schema and UI changes) between environments is this article https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/introduction-solutions

Solutions allow you to move schema changes to different environments without having to repeat the configuration.

With regards to publishing changes. V1.0 and V1.1 point to the same database. The difference being is that only you (as the customiser) will be able to see the v1.1 changes in the UI if v1.1 is unpublished. Once you publish v1.1 all other users will see it.

I hope this helps.

[v-xida-msft · Accepted solution]

Hi @ghdunn ,

For your first question, both v1.0 and v1.1 point at the same underlying database. If you do not publish v1.1, other shared users would not be able to access the changes you made in your V1.1, they could only be accessible to current published version of your app.

For your second question, if you want to migrate a canvas app from one Environment to another one, I think it is not necessary to replicate the changes you made in your Dev Environment within your Prod Environment. I agree with @HSheild's thought almost, I think the Solution functionality may be a better choice for you.

Solution in PowerApps

You could add a Solution in your PowerApps, then add your canvas app into this Solution, then export this solution, then import this exported solution into other Environments, after that, you could use the canvas app in other Environment.

Best regards,