PowerApps - Connections will not delete - Allow / Don't Allow keeps coming back

[sgregory]

I can't seem to get rid of orphan connections... There are no data souces used for these connections. In previous version of the app I was testing how to set up connects. Once I figured out how and what method I wanted to use I then removed the data sources and the connections for it. But they won't go away and it is keeping the connection I do need to use from being able to use it.

Each time I open the app I have to delete all the data souces and then re-connect to the SQL Server connection I actually do use.

I have tried everything from saving the app then re-importing it to see if that help. It doesn't...

I've tried deleting old versions of the app and only keeping the ones that use the connect I need. That doesn't work.

I've tried creating a new app and coping the objects (screens, buttons, etc.) to the new app but it won't allow me to do that either.

I can't have end-users removing data sources then adding them back in each time simply because of these orphan connections.

[NMatGWM2]

There are multiple "dependsOn":[] sections from what I am seeing....  how to know what and where to cut?

[PaddyWann]

Having same issue with Docusign. no amount of saving and opening helps. 

[Pstork1]

Saving and opening won't help because the app has cached the configuration of the connection so it thinks its still there. To get rid of a connection you need to either roll the app back to a version before you added the connection or delete the connection in the main Power apps site. rolling back a version will lose any work you've done since then and deleting the connection will delete it from every app and flow where it is currently in use. But other than disassembling the app and hand editing the source code those are your only options.

[sgregory]

I would give Microsoft a quick call. You may need to export the app and remove the connection from it that way then reimport the app back in.

[PaddyWann]

Ok, I tried deleting the connection to avail.  I will make a new app and copy paste as much as it will let me.  This is a major bug that should be fixed. I'm ready to launch and now I have to do this. I shouldn't have to deal with this. (my common catch phrase for the power platform)

[sgregory]

I totally agree with you. PowerApps is a bit clunky. 

[leonsig93]

From what I noticed with the Outlook 365 connector (we had issues with flows not working), removing it from the app was as simple as removing the connection from the app. Our issue was that even though it was completely removed from the app and the connected flow, it had stored it as an active connection within the flow. So since the flow was a PowerApps trigger, the app kept trying to use the connection.

In my case, I had to remove the flow and recreate it from scratch. Once I connected the new flow without the Outlook connector, my app stopped asking for the connection. So definitely double check any connected assets and see if the issue is starting somewhere outside of PowerApps itself. Obviously this won't apply if you don't have anything connected.

All in all, agree with the sentiments. A lot of weird behaviors that we shouldn't have to deal with.