cancel
Showing results for 
Search instead for 
Did you mean: 

I would appreciate a fix so that when I import a solution that includes a connection to an on-premise SQL Server into another environment, I can allow the connection without having to edit Power Apps.

I have created a solution that includes Power Apps and Power Automate with a connection to an on-premises SQL Server.

 

I exported this solution and imported it in another environment.

 

Then, when I regenerate PowerApps, I get a popup asking for permission to connect, but the SQL Server connection that appears there says "Your app needs this connection. Please edit the app and add it again" and the connection cannot be allowed.

 sqlconnection.png

In the imported environment, editing Power Apps, deleting all SQL Server connections and re-adding the same one resolves the issue, but it is very time consuming.

 

I would appreciate a fix so that when I import a solution that includes a connection to an on-premise SQL Server into another environment, I can allow the connection without having to edit Power Apps.

Status: New
Comments
alperschwede
Regular Visitor

Hi @yukah,

 

this already works, even if the procedure is not entirely intuitive:

 

  • Add a connection reference for the SQL connection in the solution.
  • Create the SQL connection to use in the target environment and share it for use by your organization
  • Import the solution into the target environment and point the connection reference to the shared SQL connection

Once you have completed these steps, users can allow the connections.

 

Best,

Alex