There is a problem when modifying an already used Flow. If the modification is adding or removing parameters for the flow there is no way to "Refresh" the Flow in PowerApps. The only way is to remove the Flow from PowerApp completely and add it back again. But this process does not work when you changed the Flow name during import of the PowerApp. Here is an example:
My app is using a flow called CreatePOPDF. I created a copy of the app in the same tenant using export/import process. This copy is to have a dev/test environment that is separate from production version.
To distinguish both copies the dev version has "(dev/test)" string added to app and Flow names during import process. Thisa results in following Flow being listed in data sources:
This means that e.g. in "OnSelect" of the button that triggers this action it calls CreatePOPDF.Run(...) even though the actual name of this Flow is "Create PO PDF (dev/test)".
Now when I update this flow with new parameters I need to remove the flow above and and the flow again. This adds the new flow but the call to the flow changes to "'CreatePOPDF(dev/test)'.Run(...)". This makes any other calls to this Flow incompatible. Moreover the this makes my dev/test copy incompatible with my production version (flows called by different names).
Is there a way to add a Flow the same way that import procedure does (calling the flow in the code by a different name than the actual Flow name)? Why Flow's do not have the same "Refresh" function in PowerApps as other data sources have to avoid the "Remove"->"Add again" procedure?