ALM RECOMMENDATIONS FOR THE POWER PLATFORM
At a previous workplace, developers were using different development methods in Power Platform, which caused permission issues when multiple develoeprs worked on the same project, as well as causing productivity and organisational issues, which caused immense difficulty in identifying what components were involved in the project.
The PowerApps environment is not typically designed for a team of people to work together to produce apps, although Microsoft seems to be adding features over time to support this. The most solid advice I have found is the following blog post, titled Establishing an Environment Strategy for Microsoft Power Platform.
I developed and implemented a strategy to overcome these issues, as well as integrate the PowerApps environment with Azure DevOps for source control.
Key features included
- a centralised development environment, the solutions in which would automatically flow into a backup Git repository
- a strategy for managing Connection References in solutions, to eliminate dependency issues. Each solution was only to have the components that were required for it, with Connection References being stored in a shared 'Connection References' solution that would then become a dependency of the project solution. This Connection References solution could then be manually deployed to Production Environments, and Connections would only need to be specified once per Connection Reference, minimising chance of error.
- an Azure DevOps pipeline for automatic deployment of solutions from Dev to Prod
The guidelines worked well, and would save newcomers many hours. Please comment below if you would like any further information.