Server Response: Principal user is missing prvRead[Entity] privilege - data doesn't load

[Anonymous]

I've added new users to the PowerApp and while they have the correct permissions enabled (i.e., they're designated as a CDS user in Dynamics), when the user loads the PowerApp they encounter the message: "An error occurred on the server. Server Response: Principal user (Id=<userid>, type=8, accessMode=1, roleCount=2) is missing prvReadAccount privilege (Id=<id>)" and nothing loads in the app. The error messages flash frequently and cycle through all of the other entities, both standard (e.g., Account, Contact) and custom and then eventually stop, but still no data loads. As you can see in the attached screenshot, users are able to view the structure of the app but there's just no data present. Other users have no problems, despite having the exact same roles and permissions. I've tried revoking then regranting privileges, as well as designating the new users as System Administrators, but nothing works. Is this a known issue and how can I fix it?

[v-xida-msft]

Hi @Anonymous,

Based on the error message that you provided, I think the end user has not been assigned a proper permission to access your CDS Entity.

When sharing an app which connects to a CDS Entity with other users, you must also ensure that the users who will run it have the appropriate permissions for the entity. You must firstly define a security role which has proper permission to perform tasks such as creating, reading, writing, and/or deleting within the relevant entity, and then assign the security role to the other users.

More details about managing CDS Entity permission, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/share-app#manage-entity-permissions

Please check and see if the following blog would help in your scenario:

https://community.dynamics.com/crm/b/crminogic/archive/2016/02/19/error-principal-user-is-missing-prvreadaccount-privilege-resolved

Please check if you have assigned proper security role which has enough permission to perform tasks within the specific entity to the other users.

Best regards,

Kris

[Anonymous]

Hi Kris,

I do have the proper security roles assigned. All of the users have the same roles but only some are getting this error message. I have no idea why because they're identical. I think this may be a bug in PowerApps. 

[Simmo86]

Hi, 

Did you ever resolve this? I have the same issue and have gone through all the help texts and assigned all roles etc. but get exactly what you get. 

Thanks,

Alex

[Som_Maganti]

Can anyone post if this is resolved - getting a similar error and permissions seem enabled

Thanks

[Thoman]

This guy did a fantastic video on this issue. The articles that Microsoft have posted are not detailed enough on how to create the new Security Role with permissions to your Entity.

https://www.youtube.com/watch?v=5gIwP4bnPy4&feature=emb_title

[marccontrtact]

I hit this when trying to assign a user as Team Administrator. The problem for me was that the user I was trying to assign hadn't net logged into powerapps and accessed that environment. After the user logged into power apps and switched to the environment. Then I was able to assign them without issue.

So this tells me the CDS is how half the environment security is managed. And the CDS is not populated with user information for users that have not logged in yet.

The fact the security is so different in management for a database vs non-database enabled environment is of much concern and leads to confusion and likely misconfiguration by administrators/users.

[Vetri_T]

"Principal user is missing prvRead[Entity] privilege", I had the same error in our Dynamics 365 CRM. this error prevailed even after assigning the user with "System administrator" security role.

after some googling I was able to clear that error by adding the specified entity (in my case it was a custom entity that I created but did not add to the newly created model driven app) to the model driven app.

once the entity was added to model driven app the error is gone.

if you found this useful, make sure to upvote so others can save find this 😊.