Microsoft needs to fix Custom Connector refresh when importing solutions containing changes to custom connectors.

Imagine the following scenario you have solution "TestSol" deployed in Test Environment as managed version 1.0.0.0

This "TestSol" solution contains a customer connector that is being used in a Canvas App.

Before, you developed "TestSol" in your Dev Environment. There the solution is unmanaged.

Now let´s say, you did some changes to the custom connector and exported the solution as managed again, version 1.0.0.1 and imported it in the Test Environment via PowerApps pipelines or Azure Devops (the right tools, since we want to have an ALM process for a real project).

How come there is a limitation stating I must need to go manually into the canvas app and perform a refresh on the connector (and hence creating an active layer) in order for the connector to be updated in the Test Environment ?

This goes against good all ALM practices! It is asking for human intervention. I know that this is reported in the documentation:

Use a connection reference in a solution - Power Apps | Microsoft Learn

But this should be fixed ASAP, otherwise using one of the most powerful tools in Power-Apps (custom connector development) is severely injured and as a result, we cannot create a proper ALM pipeline.

Microsoft would only benefit from this because this is discouraging the use of PowerApps Pipelines (which currently is monetized in prod and DevOps).

Why would I want Devops if it will not work with updating custom connectors ?

Categories:

Authentication

Quick Links

Leaderboard > Power Apps