cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Kudo Collector
Kudo Collector

Re: Could not find connection 'cbaaf7feb51741fca497ac3d7566c5fb' for API 'shared_sql'.

So... why is this one solved while there is no solution?

 

Working with multiple environments:

I managed to get the permission request go away by re-adding the connection, removing the connection, saving as a new PowerAppConnectorFree, exporting PowerAppConnectorFree, importing PowerAppConnectorFree to update already existing PowerApp --> no more permission popup request in already existing PowerApp in this environment.

 

However the already existing PowerApp is part of a Solution so when exporting Solution after all the above with this now correctly functioning existing PowerApp and importing the overall Solution in a brand new environment --> the permission popup request is back again 🤯

Highlighted
Advocate I
Advocate I

Re: Could not find connection 'cbaaf7feb51741fca497ac3d7566c5fb' for API 'shared_sql'.

Hello everyone,

 

Same problem here...any new solution? I have so many connections that I can't even find witch one is causing the problem.

What is the difference between "exporting" and "saving as" a file ".msapp" in your computer and then uploading it?

 

Thank you.

Highlighted
Frequent Visitor

Re: Could not find connection 'cbaaf7feb51741fca497ac3d7566c5fb' for API 'shared_sql'.

i got exact same problem cant export it.My project is very big 😥

Highlighted
Frequent Visitor

Re: Could not find connection 'cbaaf7feb51741fca497ac3d7566c5fb' for API 'shared_sql'.

Am witnessing the same problem 😞

I am sure it is a bug in PowerApps/Automate connections.

 

MY PowerApp shows several Flow connections. I have removed all references from the Data Tab as shown.
Have spent hours trying to figure out the problem.

Highlighted
Frequent Visitor

Re: Could not find connection 'cbaaf7feb51741fca497ac3d7566c5fb' for API 'shared_sql'.

I was running into the same error saying that power automate "Could not find connection" for a SQL server connector I was no longer using in my project. However, I was able to successfully export the project after the following steps:

 

1. Identify the connector(s) causing the error/no longer in use

2. Edit the flow and add any action step that uses the connector throwing the error

3. Delete the action step

4. Export the flow



Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Watch Now

Experience what’s next for Power Apps

See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Top Solution Authors
Top Kudoed Authors
Users online (7,622)