Hi!
I'm having some problems sharing my application with two of my colleagues (or really everyone in my organization). Specifically the two users I've shared my application with recently is not able to execute some of the flows from within the application. When saying not able to execute I mean not able to run the flow at all. However, this does not apply to all of the flows.
All flows etc. are included in the solution.
Data source: Sharepoint
The users get two different error messages.
This user have access to the development environment.
Copydatafromtasklist.Run failed: {"error":{"code":"0x80048306","message":"Principal with id ... does not have ReadAccess right(s) for record with id ... of entity workflow. Details: {\"CallerPrincipal\":{\"PrincipalId\":\"...\",\"Type\":8,\"IsUserPrincipal\":true},\"OwnerPrincipal\":{\"PrincipalId\":\"...\",\"Type\":8,\"IsUserPrincipal\":true},\"ObjectId\":\"...
This user does NOT have access to the development environment.
UpdateCompletecolumninTaskList.Run failed: {"error":{"code":"0x80042f09","message":"RetrievePrivilegeForUser: The user with id ... has not been assigned any roles. They need a role with the prvReadWorkflow privilege."}}
I should add that I have shared this solution / app with two other users before Christmas and it works for them. These two users were also added to the "same" solution in my "Personal Production" environment before I exported the solution to the development environment in mid December. None of these two users have access to the development environment AFAIK.
If I share the flow as "Run-only users" it seems to work. However, I would prefer not to do this for all my individual flows.
The way I understand the documentation it should be sufficient to share a solution with the user and not share each individual flow as well. It is also the way it works for the two previous users I've shared the application with.
https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/share-app-resources
I've found others struggling with the same issue, and it seems like the way to solve it is to add users to security roles in the environment, but I don't have permission to do this, and I assume it would be better to find another fix if possible.
https://powerusers.microsoft.com/t5/Microsoft-Dataverse/Dataverse-Security-Roles-Solution-with-SharePoint-Canvas-App/td-p/2343509
https://powerusers.microsoft.com/t5/Power-Apps-Governance-and/RetrievePrivilegeForUser-The-user-with-id-id-has-not-been/td-p/1917584
One of my colleagues asked if there was anything special with the flows that this occurs for (which is by the way most of the flows).
My answer to him was.
I'm not sure what is special with the flow which this occurs. I've tested this with one more user now. I got two basically identical flows. One works and the other doesn't. This applies to all three users (initially, I'll explain in the end). They have the same connection references, both linked to the solution etc.
Working flow:
Not working flow:
Working flow:
Not working flow:
When saying it applied to all three users initially i refer to this.
"Another strange behavior I noticed is when I shared one of the flow as "Run only users" it worked for both as expected, then I removed the permission for the two users again, and the flow still worked for one of them (the one outside the environment). Not for the other one though."
I've recreated this with user number two now. I had him as "Run only users", it worked, I removed him again, and it still works. This happened the second time we did this. The first time it stopped working when I removed him from "Run only users". The flow I refer to as the working flow has worked for all three users on the first try without doing anything special.
So by looking at these two flows I'm unable to pinpoint anything that can be causing this problem.
I can also add that user number two changed web browser from chrome to edge after I removed the permission on the "not working" flow, and it still works in edge, so I don't think this weird behavior of the flow working after the permission is removed is related to cookies at least. Maybe the connection fixes itself when they run it with "Run only users" permission, and when I remove the permission the connection continues working.
