Hi all,

I wanted to know what kind of approach you are using for a serious and reliable Application Lifecycle Management (ALM).

We are currently using pipelines for the first deployment, working fine.

But now we face the issue that the managed solution gets some upgrades from time to time.

We also want to deploy those. We needed to adjust certain settings we don't want to deploy the entire solution again.

Especially dataflows are not working well as the production needs other connections as the dev or test envr.

What would be the best way to deploy changes?

We currently deploy a new solution which contains some upgrades, but I would rather not have a new solution for each upgrade.

As far as I know I can't tell the pipeline to upgrade only certain flows, apps etc. Same goes for the import/export approach.

Any suggestion is highly appreciated.

Categories:

Microsoft Dataverse with Power Apps

After some time we finally found a solution to update a single change for a managed Solution.

Patching a solution

Process

A solution can usually be deployed via pipelines. In case you just want to create an update there seems to be only one solution currently.

Your prod solution is managed and on another environment than the dev solution
Your dev solution is in an unmanaged environment.
You can export the the solution as unmanaged and will receive a .zip-file
Import that solution to the prod environment.
You can now create changes with a patch solution in your dev environment.
Export the patch and import the newly created patch solution into your prod environment.
Merge the patch with the first solution inside your prod environment with "Clone a solution" and you will now have an update on your prod environment.

Additions

The patch solution seems to override the unmanaged Layer, in case there is one, for Power Automate Cloud Flows. You can go back after deleting the Layer. Just be sure that the flow is than back to the earliest stage. Deleting or changing something directly in your unmanaged solution in your managed prod environment will effect those things in your managed solution you first deployed.