My team and I are working on a canvas app that’s part of a solution in Power Apps, alongside some flows and other components. We've already deployed the first version from our Dev environment to Prod.
Now, we’re in a situation where:
- One team member needs to work on upgrading the app, which may take a few weeks.
- Meanwhile, others need to handle urgent bug fixes reported by users.
Here's what we've done so far:
- We cloned a patch for the developer working on the upgrade.
- However, when another developer tried to fix a minor issue reported by a user, they couldn’t edit the canvas app because:
- The original solution is locked due to the active patch.
- The patch version is still in development and not ready for deployment.
- If we create a second patch, it still references the same canvas app component, which is now shared with the upgrade work, and again is not deployable independently.
Question:
How can we manage parallel development of a canvas app — one for long-term upgrades and another for urgent hotfixes — within the solution framework?
Is there a recommended approach or workaround that allows for editing and deploying one component (the canvas app) separately without being blocked by other ongoing work?
Thanks in advance for any guidance or best practices!
