Unanswered

Workflow .Run Failed Error message -"does not have ReadAccess right(s) for record with id" - Only happens with specific users

(1) Share

Report

Posted on by pAAMckelvey

Hoping someone can help, one of our users is getting this error message, the trick is, they are the only one getting the error message, everyone else that runs the app is able to complete the task without the error below popping up.

The app calls the workflow below with the .Run command and as mentioned, the workflow runs for everyone but this one person. This user can run the app, create records and view records in the SharePoint lists associated with the app with no problem. Doesn't seem to be a permissions issue from the perspective of running the app or the data sources.

The workflow doesn't run at all when this error appears but does run for other users.

Any insight into what this error means would be helpful.

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (1)

Shaheer Ahmad 2,194 Moderator on at

Like (1)

Report

Check the user's role and group memberships in SharePoint. Ensure they are part of the necessary groups or roles that grant read access to the records.

Was this reply helpful? Yes No
v-yetonggu-msft on at

Like (0)

Report

Hi @pAAMckelvey ,
This user lacks a security role. This user lacks a security role. Please log in to this website as an administrator
Power Platform Admin center and assign him a security role.
I think this link could help you:
Assign security roles - Power Platform | Microsoft Learn
Best Regards,
Sunshine Gu

Was this reply helpful? Yes No
pAAMckelvey 40 on at

Like (0)

Report

Can you be more specific? This particular user normally works out of our test environment as our QE (quality engineer) and in the test environment for this same app she doesn't have any environment roles assigned and is able to trigger the workflow just fine.
Just as a proof of concept we did assign her the Environment Maker and Basic user with the same resulting error message.

Any further insight is appreciated.

Patrick

Was this reply helpful? Yes No
Verified answer

pAAMckelvey 40 on at

Like (1)

Report

As a follow-up, we resolved this issue by adding the user to the Run-As User permissions on the workflow in the solution. To be clear, we did not have to add this user to a role within the environment where this application and workflow reside.

Was this reply helpful? Yes No
ptmisi 3 on at

Like (0)

Report

Thank you! i had the same error and i was able to resolve it. but i also want to ask if i can use for managed solution? does it create layer? Thank you again!

Was this reply helpful? Yes No
nleuck_101 429 on at

Like (0)

Report

I'm having the same issue. It looks like when I'm in my test environment it doesn't keep the permission when I publish to the production environment. I have to readd my run as user permissions.

Was this reply helpful? Yes No