Workflow .Run Failed Error -"user does not have ReadAccess right(s) for record of entity process"

(0) Share

Report

Posted on by rpersad

825

Unsure why my flow is getting this error. My flow runs automatically on the 'On Start' property of the app and retrieves a value from an environmental variable on the app as a text value. No connections are used in the flow. From my research into this problem, people have suggested to add the user to the Run-As User permissions on the workflow in the solution, however this was due to some users not having access to a SharePoint list and to grant them to user the owner's permission to access the data, which is different to what I am trying to do.

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Infamous_Let 332 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Even though no connections are used, Power Automate still enforces security roles for accessing data and processes. You might want to check if the user has the appropriate Read permissions on the Process entity in Dataverse. Try granting at least Basic (User) or Organizational level Read access depending on your setup.

If the issue persists, check if the environment variable is set to a scope that the user has access to. Sometimes, environment variables are restricted by security roles, which could be causing the error.

Was this reply helpful? Yes No
rpersad 825 on at

Like (0)

Report
Copy link

Link copied!

HiInfamous_Let ,

The process entity does not have anything to do with Dataverse. The user doees have access to access the other environmental variables which stores the SharePoint sites/lists.

Was this reply helpful? Yes No
rameshmukka 1,121 on at

Like (0)

Report
Copy link

Link copied!

@rpersad Can you please help with the solution if you have already solved it? I have same exact issue. Running the Power Apps trigger flow throws this error everywhere on the app.

Thanks,

Ramesh

Was this reply helpful? Yes No
Verified answer

rpersad 825 on at

Like (0)

Report
Copy link

Link copied!

Hirameshmukka , I was able to solve this issue by selecting a user/group in the Run only users property of the flow, see image attached. In my case I added a group which has all the users who will be using the flow.

Was this reply helpful? Yes No