We are creating an app that relies on a Flow to send an XML file to a FTP server for signature with a private key.
Problem si that when regular users open the app, PowerApp request them to "Sign in" for the FTP connector and that means to enter the FTP server details when those are defined during the Flow definition!
Visibly a big defect.
- To Microsoft: when can that defect be fixed?
- To All fellow developers: anybody has an idea on another way to send efficiently some files from Powerapp app to a remote Windows Server file directory (also on Azure)? Thank you!
Could you please share more details regarding how the flow created?
We could take use of team flow (Flow sharing), which allows multiple users to use and edit Flow settings.
For App shared under PowerApps, the resources used in this app would also need to be shared:
For the file upload control, currently there is an idea submitted, which is planed:
Hope the information above is helpful.
Thank you for your answer.
The flow is very simple:
PowerApp -> FTP Create File with filename and content informaiton provided by PowerApps
It is called using Run in the Powerapp and works perfectly as long as it is the login that created the flow that connects.
Yes the connection sharing is what is required and the problem is the following:
It is then most probably a defect a FTP conneciton can't be shared...
Visibly the same exact problem happens with SMTP connector, see the comments at the end of the link you provided on the share of connections: https://powerapps.microsoft.com/en-us/tutorials/share-app-resources/
No solution, this seems to be a standard behavior of PowerApps. Even SMTP connectors require each use to enter his SMTP setting, that's totally dumb.
Thanks for the feedback. It should be a configuration option whether or not you want to use the same creds to authenticate all users or if you want each user to enter their creds.
We ended up building an Azure Function to transfer files from Azure Blob storage to an SFTP folder, storing the credentials in Azure Key Vault. Then exposed the function as a custom connector. Which is not ideal due to the way DLP policies work with PowerApps / Flow and custom connectors. But we had no choice, we were up against a deliverable with no fix in sight. As far as I know this is still not fixed.
We had two main issues with the SFTP connector that make it unusable, 1) the issue of requiring site properties and credentials when sharing the connector and 2) getting a very generic error attempting to transfer files to the root folder of the FTP site. All other tools (WinSCP, FileZilla, etc) were able to transfer to the root folder as was the library we used in the Azure Function, so this was not a permissions issue on the site itself.
I really wish the connectors were more powerful and less buggy. Sorry I can not report that it was fixed and there is a sinple work around.
Check out new user group experience and if you are a leader please create your group
Did you miss the call?? Check out the Power Apps Community Call here!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.