SQL Connections in a solution

Like (1) Share

Report

Posted on 24 Jan 2023 16:49:44 by dakridge

191

I have created a canvas app that uses a SharePoint list and an SQL database for lookup. I created this in a solution that has the site reference and the environment variable to connect to the SharePoint. I have added a Connection Reference to the solution that points to the SQL database. I'm not concerned about implicitly sharing because there is no sensitive data and it is read only. When I export the solution and move it to a production environment, it is not moving the SQL connection. I have searched for a while and cannot find a reason.

Can someone give me the proper technique for having this connection reference move to the production environment, or do I have to create an identical copy of the connection in all environments?

Thanks

Categories:

Connecting to Data

Connectors

All responses (2)

Answers (1)

Verified answer

dakridge 191 on 31 Mar 2025 at 19:33:23

Like (0)

Report

SQL Connections in a solution

Using Pipelines solved this issue.
kylzbaba 182 on 19 May 2024 at 09:50:22

Like (0)

Report

Re: SQL Connections in a solution

Hi David,

I am afraid I do not have a more concrete solution for this but all the same I will share the solution that has worked for me so far.

1. Creating the SQL connection afresh in the new app inside a solution and not choosing an existing one. This creates the connection as a new shared connection and will treat it as the regular flow connection reference when you try to import the solution. The downside is that you to do this everything you are creating a new app. The SQL connection must always be created afresh in a new solution, you cannot use it across several solutions.

2. The second solution to use Power Automate to perform all CRUD operations. This way it uses the flows connection reference and you won't have any issues with not being able to reference the connections within Power Apps. The downside to this is, you end up doing a lot of work setting up read and write operations. It does keep your app super light though.

It is sad that Microsoft still has not done something about this, it really extends my build time since SQL is the default database of my organization.

If you have found a more appealing solution, please share.