Answered

Issue with flow running in power app for other users

(0) Share

Report

Posted on by CP-93

I've made a leave request app for staff, I've tested it and it all works, but once I have someone else try and use it they receive this error when they hit submit which should trigger the flow.

Any ideas?

Categories:

Using flows

I have the same question (0)

All responses (9)

Answers (1)

ChadVKealey 1,393 on at

Like (0)

Report

I'd suggest using Monitor to get more information about what's causing the error. See https://learn.microsoft.com/en-us/power-apps/maker/monitor-overview

If it works for you, but not others, I suspect it's something to do with permissions. Do the other people using the app have access to the data sources it's using? Sharing the app doesn't automatically share those sources, and flows triggered from an app will ALWAYS run in the context of the user of the app.

Was this reply helpful? Yes No
CP-93 55 on at

Like (0)

Report

Thanks,

most of the data sources are using my account, but when I tried changing them to a service account the flow would fail because it was using the service account for the get manager function instead of which user had filled in the app fields

Was this reply helpful? Yes No
ChadVKealey 1,393 on at

Like (0)

Report

If you mean the "connection" in each action in the flow, that's irrelevant for a flow that's triggered from an app. When the app is shared, the flow is shared with it, effectively making the app users "run only" users of the flow. When you add "run only" users to other types of instant flows (e.g.: "For a selected item" in SharePoint), you can specify whether the flow will use the connections defined in the flow, or the connection of the run only user. When a flow runs from a Power App, you cannot designate which connection will be used; it will always be the connection of the person currently using the app, regardless of what connection you set in the flow. So, unless the users are signing into the app with the credentials of that service account (which they probably should not be doing), the flow is running as them.

Was this reply helpful? Yes No
CP-93 55 on at

Like (0)

Report

Thanks for such a detailed response! So do users need to be given access to the flow or are you saying just by using the app they’re given run only rights?

Was this reply helpful? Yes No
Rajat Awasthi 37 on at

Like (0)

Report

Hi @CP-93 ,
Do you have the failed Flow run log. Can you please share us with that. I believe there is something wrong with tables access you are using in the Power Automate. Failed flow run would have captured the failed step and error.

Was this reply helpful? Yes No
ChadVKealey 1,393 on at

Like (1)

Report

You don't need to explicitly share the flow, but you do need to share the data source(s). So, if users of the app will be creating or editing items in a SharePoint list, they need appropriate permissions to that list. The easiest option is to give them Contribute access. However, this also allows them to directly access and edit data in the list, which (in most cases) app designers would like to prevent. There are various tricks to prevent that direct access, but many are "smoke & mirrors" or "security by obscurity". The most effective method I've found is using a custom permission level. See this video for more details: https://youtu.be/x06Qag5YaZs

Was this reply helpful? Yes No
CP-93 55 on at

Like (1)

Report

It seems like the flow isn't being triggered when other users hit submit..only me?

Was this reply helpful? Yes No
nsyyoung 6 on at

Like (0)

Report

I had the same problem, but it went away when I explicitly shared the app with my user. She had access to the data sources, the site, and the app, but the flow wouldn't run until I actually shared the app with her.

Was this reply helpful? Yes No
Verified answer

CP-93 55 on at

Like (0)

Report

It turned out that you need to use power apps V2 as the trigger this gives you the option to have 'Run as Only' users.

Was this reply helpful? Yes No