How to disassociate unused Flows and Connectors from Powerapp

[martinav]

I have a powerapp that I have saved a copy and reduced to base minimum in order to eliminate the need for file system connectors.  However, deleted screens and all commands referring to Flows that call for these actions do not disassociate from the app.  Despite my deleting them from my 'Data' menu in edit mode. 

Note current associations in app:

When I look in 'details' for the app, I still see all the old Flow associations.  This triggers the need for File System actions.  Subsequent Save-As does not eliminate these associations either.  Please advise.

[RandyHayes · Accepted solution]

@martinav 

The quickest way is to export your app and then import it back in.  That will remove the references.

The harder way is to fiddle with the JSON of the app itself in visual studio.

I hope this is helpful for you.

[martinav]

@RandyHayes ,

Well, the easy way has taken 2 hours, to no avail.  I need the hard way.  I have export inport ALL flows associated with this app.  I've checked and there is NO reference to file system in any of the flows.  It MUST go.  I'll edit a JSON file, whatever it takes.  How, where, etc.

[RandyHayes]

@martinav 

Well first off - how were you exporting and importing?  I should have been more specific on it!  What I would suggest was to open the app in the designer and then perform a Save As and then save to a file on your computer.  Then create a new app and then open that exported/saved file.

If you've not tried that, give it a shot and see if that removes it.  Then the hard way!

[martinav]

@RandyHayes ,

Well, these were my attempts:

1.  Like you said.  I opened in designer, Save-As.  No change.  All references to connectors and old flows remained.

2.  I did an Export, then re-import.  I set each connection to update, including the app.  Connections and flows remained.  

3.  I did the same as #2, but set the app to "Create New".  This resolved the old flows and some of the connectors.

4.  I checked flows.  One flow that had no file system actions showed a connection to file system.  I did an Export/Import to that flow.  The flow was resolved.

5.  I redid #3, thinking this would resolve.  No.  File System connection reamins.  

6.  I'm out of time and methods.

[RandyHayes]

@martinav 

So the issue seems that you had a flow with the connection and your app was using that flow.

You have removed it from the flow - that is good.

Did you edit the app, save it and publish it??  When you export an app, it will export the published version.  So, if the app did not get updated after you updated the flow, then it would still be exporting the same old stuff.

[martinav]

@RandyHayes 

I did the import as create as new.  Also, deleted the flow from the app... readded.  no avail.

Its this kind of crap that I waste more time on than doing complicated coding.

[RandyHayes]

@martinav 

Yes, but my point in the last reply is, are you publishing the app after the changes?  This is important for the export.

[martinav · Accepted solution]

@RandyHayes ,

Yes, I have been publishing after changes.  

I'm not sure what all worked to fix this... I think it boiled down to these two things:

1. Ensure ALL flows are not associated with the connector you are trying to eliminate.

2. Export app, then re-import as 'new' app.  Update current app does not work.  (This is actual export/import.  In my case, save-as did not disassociate unused flows nor connections)

Unused flows do not disassociate gracefully either.  Re-import as a new app is also required for this.