You’re offline. This is a read only version of the page.
Hi,
I have a solution that contains a bunch of tables, environment variables, app, flows, etc.
I have a Flow that is using a PowerApps Button as a trigger, collects some information in the app, send it to the flow, creates a file and send back the URL of that file to PowerApps so it can be launched in another tab. This part has always worked fine in my DEV environment for me (User 1) and the a co-worker (User 2).
I exported the solution into a managed on in my UAT environment.
When I (User 1) press the button in the app, it works fine but when User 2 tries to do it, it doesn't even trigger the Flow. It does nothing.
And since this is a managed app, I can't go in edit mode to see if there's an error message or not.
All I know is that it worked for everyone in DEV and now it only works for me (owner of the solution, app and flow).
What could be the problem?
So here's what resolved the issue. There was multiple issues but it seems to be working now.
Hi @Anonymous,
Have you solved your problem?
Do you mean that another co-owner user could not access to the flow when export to another environment?
Actually, a quick fix that you could try is to remove the flow connection from the app and re-add them again. If the issue stays, I think you should check the permission for the User2 in the UAT environment.
Within Security, select Permission Sets, there is a doc about manage the existing environments:
On your side, please go to the Security Roles List in your UAT Environment, then find the Security Role which is assigned to User2, and open it. Then within the opening Permission panel, check if the Process has assigned full access to the User2.
#1
Michael E. Gernaey
497
Super User 2025 Season 2
#2
David_MA
436
Super User 2025 Season 2
#3
Riyaz_riz11
244
Super User 2025 Season 2
Share
Report
All responses (
Answers (