Hello,
When you enable concurrency in an instant workflow (Triggering in PowerApps), the workflow steps are triggered with the account of the workflow owner and not the credential of the User who triggers the workflow.
I'm using this to create items in SharePoint with the admin account and not the account of the person triggering the workflow.
I use this to secure my list. I can set the user in "Read Only" and they have to use the PowerApps application to create or modify element in the list. This is very useful for forcing people to use the app rather than the list.
Since yesterday it no longer works, it's the user's credential that's used. So in the SharePoint list, items are created by the user and not the admin account.
Has Microsoft communicated on this change in functionality ?
Do you have another idea to create an item in SharePoint from PowerApps with a different account than that of the logged in user ?
Thanks for your help.
Solved! Go to Solution.
Although I am not 100% certain, I believe that there was a change recently. My understanding is that the work around is to have the Flow triggered by Power Apps call another Flow. The child Flow will run in the context of the account used for the connections - usually the Flow creator/owner.
Although I am not 100% certain, I believe that there was a change recently. My understanding is that the work around is to have the Flow triggered by Power Apps call another Flow. The child Flow will run in the context of the account used for the connections - usually the Flow creator/owner.
Thank you. I used the child flow and that solved my problem.
https://docs.microsoft.com/en-us/power-automate/create-child-flows
https://flow.microsoft.com/en-us/blog/solutions-in-microsoft-flow/
User | Count |
---|---|
23 | |
14 | |
13 | |
10 | |
9 |
User | Count |
---|---|
51 | |
29 | |
29 | |
24 | |
22 |