See a couple of similar questions regarding this.
PowerApp calls a FLOW and that in turns creates a file via the File System connection.
Sharing the PowerApp, each user now is asked to sign into the File System connection and enter folder root path, domain\user and password.
This makes deploying the app to ~1,000 users very difficult.
Are their any workarounds on this?
Yes--write it in a way so that the users are not calling the flow directly--if I push a button in an app that calls a run command and triggers the flow, the flow must be shared with me and connect as me. If i do something in an app that updates a database like cds, SQL, or SharePoint, and that data change triggers an automated flow, that flow for 1,000 users will run under the same connection. It is also safer because I don't have to make all users co owners of the flow.
So instead of having the app call the flow, have the app trigger the flow via a data condition. Use automated flow not instant flow
Yes, did that for another app where I needed the FLOW to run as the 'utility' account, but did not think about the File System connector. Good call!
I really wanted this app to be real-time, but will have to settle for near-time. Any thoughts on the system FLOW trigger when new created is faster as List+Attachment or Library Document for the staging area?