Let us take an example of the below Entity List configured for Case entity configured for Active Cases view.
For Entity Permission to work we need to check Enable Entity Permissions.
Let us first create an Entity Permission record with Global Scope and Read Privileges and assign it to a custom web role to which in turn is assigned to the Portal User.
Below we have Case Entity Permission record associated to our My Custom Web Role.
My Custom Web Role is then associated with the portal contact record.
Scope – Global with Read Privelges à
This shows all the Active Case records in the portal.
Now let us change the Scope to Contact, and specify Conact_As_Primary_Contact as the relationship to be considered i.e. Contact Lookup in Case entity form.
Scope – Contact
This shows all the case records that has current portal user as Contact as well as those records which has Customer specified as the account which is the Parent Account of the current contact portal user.
The portal view is filtered based on the Contact Scope Entity Permission.
Now let us change the Scope to Account, and specify Incident_customer_accounts as the relationship to be considered i.e. Customer Lookup in Case form.
Scope – Account
This shows only those case records that has Customer specified as the Parent Customer of the current logged in Portal Contact User.
Hope it helps..
5 thoughts on “Understanding Scope (Global, Contact and Account) in Entity Permission in Portal (Dynamics 365)”
Nice article. Thanks.
LikeLiked by 1 person