Flow ran from app fails due to ReadAccess rights

[BradonK]

Hi all,

Been building an app that uses a flow to generate a document with data from the app.

When you click a button in the app, the flow runs and generates the document.

This works flawlessly when I use the app. I am the creator for the app as well as admin in the power apps environment.

However, when a user I have shared the app with does it, it fails with an error which I have simplified below.

Flow.Run failed error: Principle with ID (long id here) does not have ReadAccess right(s) for record with id (another long id here) of entity workflow.

Let me know if this is not enough and I will share the full error.

I have created a security roll based off of basic user and made sure all the Dataverse tables I use are set to environment.

The user I shared the app with is in this security group.

Not sure where to go with this one. Appreciate any help.

[v-xiaochen-msft]

Hi @BradonK ,

Please try to set read permission to organization.

Best Regards,

Wearsky

[BradonK]

Hi @v-xiaochen-msft ,

All of my custom tables have their read access set to Organization.

Do you mean set the "Process" table read access specifically as you have shown in your post?

[v-xiaochen-msft]

Hi @BradonK ,

Yes, the error shows the user needs this permission from Process table.

Best Regards,

Wearsky

[BradonK]

Hi @v-xiaochen-msft ,

That did appear to fix that error but now there is a new one stating the flow could not be installed...

GenerateITPDocument.Run failed: {"error":{"code":"0x80048d06","message":"Failed to install the flow"}}

[LeePope]

Did you find a solution to this? I have the same problem.  Created an App with Flow's, moved from DEV to UAT, and users cannot use the app as they get this error.  

They have a user role that has org rights on Process.  It's the "Failed to install the Flow" error that happens now. But it runs fine for me, and for co-owners with elevated permissions.

[LeePope · Accepted solution]

I actually managed to resolve this today. It did seem to be an issue with the import of the solution that contained the Flow(s). My approach might have been a little more than needed but this is what I did:

1) Commented out any reference to the Flow(s) in the app.

2) Removed the Flow(s) from the app in target environment.

3) From the imported solution, removed the Flow(s) from the target environment.

4) Created a new solution and added just the Flow(s) and their required objects - connection references in my example. 

5) Exported and imported the solution again. 

6) Added the Flows back into the app in the target environment and removed commenting. 

All working as expected this time around. I've done many solution exports and imports and this was the first time I've seen

[BradonK]

Hi @LeePope ,

I tried to follow your steps but it didn't seem to work for me. Can you clarify exactly what you did?

This is what I did:

1. Comment out references to the flow in the app (Dev Env).

2. Removed the flow from the flow menu in the app (Dev Env).

3. Removed the flow but not the connection references from the solution (Dev Env).

4. Exported and Imported the solution from the Dev environment to the Prod environment.

5. Added the flow back the the solution (Dev Env).

6. Added the flow back to the flow menu in the app (Dev Env).

7. Removed commenting in the app (Dev Env).

8. Published app changes (Dev Env).

9. Exported app from Dev environment and imported to Prod environment.

The issue still occurs.

Thanks

[LeePope]

@BradonK - Sorry it didn't work 😞

I am moving from DEV to UAT and it seemed that most of my changes were needed in my UAT environment.  It was almost like the previous import had corrupted somewhere along the line, specifically with the connection references...

I deleted the Flows and connection references from UAT (in your case, PROD) completely, but left the app there with the Flows removed and code that referenced them commented out. 

I then went back to DEV, created a new solution that contained the my two Flows (one was calling an API and another linked to SQL) and for each Flow "add required objects" from the ellipses. 

That meant I had a new solution with 2 Flows and 2 connection references in.  

I imported this solution to UAT.  
Opened my UAT app and added these Flows back in and then removed my commenting out.  

Users were then able to access the app, establish their connections and proceed without the error.  

Keeping fingers crossed for you...

[BradonK]

Hi @LeePope ,

So I may have dug myself a bigger hole...

My Prod solution is managed and so I can't remove items from it. So I simply deleted the entire solution!

There was no data I was worried about losing in it yet as It hasn't been rolled out, so I thought, "if It's corrupt, delete it."

Anyway, I reimported the solution. But now I can't seem to add the Dataverse tables back to my security role as they are not showing up. I am going to troubleshoot this further, but will get back to you on if it fixes the original issue.

Thanks for the help so far.