🚨

Resolved: User does not have ReadAccess (rights) for record with id

Table of contents

The error
Step by step explained
Error message
The solution

☝

TL;DR - When importing solutions into a new environment, users weren’t able to trigger flows from a Power App anymore. This meant going into the productive app, deleting flows connections and re-adding them to the app. Unnecessary and it would create an unmanaged layer when editing a managed solution. With this fix you can get rid of that error.

The error

Step by step explained

I have built a Power App that is part of solution. In that solution are two or more flows that are triggered from buttons in the Power App. While developing in environment A flows can be triggered without any issues. Once the solution is imported from environment A to B as managed the flow cannot be triggered from the app anymore. The error message describes that the user does not have read access to the flow record in dataverse.

Error message

In plain words: The current user (with id …) cannot read the flow (with id …) from the dataverse store and therefore cannot run it.

The solution

You need to be Power Platform or Global administrator to do this. For this is would also make sense to work with Teams in environments to assign correct roles and permissions.

Open Power Platform Admin Center > Environments
Select the environment that has this issue, then click on Security roles

💡

I am assuming that in this environment the users will only use apps and flow and not create any entities.

Navigate to the Basic User role and copy the role. Call it “Basic User Fixed” or any other name you see fit.
Select your newly created roles from the list. Then scroll down until you find the entry with the table name “Process”.

In this record change the Read Property to at least “Business Unit”.

Now assign this role to either the User or the Team.

💡

Not sure what Teams in Power Platform are? I also have an article about Teams in my blog.

Thanks for reading! 💕