{"id":2947,"date":"2018-04-10T12:50:17","date_gmt":"2018-04-10T12:50:17","guid":{"rendered":"http:\/\/himbap.com\/blog\/?p=2947"},"modified":"2018-04-10T12:50:17","modified_gmt":"2018-04-10T12:50:17","slug":"accessing-cases-of-sub-accounts-dynamics-365-portal","status":"publish","type":"post","link":"https:\/\/himbap.com\/blog\/?p=2947","title":{"rendered":"Accessing Cases of Sub Accounts- Dynamics 365 Portal"},"content":{"rendered":"

Requirement<\/strong>: Dynamics 365 Portal user should be able to access cases from it\u2019s parent customer as well as sub account of it\u2019s parent customer.
\nSolution<\/strong>: We can implement this requirement using Web roles where we can configure entity permissions to access sub accounts and cases in dynamics 365 portal. We need two following entity permissions here:
\n1. Entity Permissions to access cases from parent customer
\n2. Entity Permissions to access cases from sub accounts of the parent.<\/p>\n

We are implementing these requirement in our Dynamics 365 portal trial, if you are new to portal and want to configure your trial quickly, you can refer this KB: https:\/\/docs.microsoft.com\/en-us\/dynamics365\/customer-engagement\/portals\/provision-portal<\/a><\/p>\n

You can check our earlier\u00a0article to create portal dev users quickly.<\/a><\/p>\n

By default portal contains entity permissions configured for different entity at different levels. For our first requirement we can use existing entity permissions, so let\u2019s configure our web role using following steps:
\n1. Navigate to Portal->Web Roles->New and let\u2019s say we want create web role as Portal Support User<\/strong> so enter name and keep other fields as default and click on Save.
\n2. After save click on the V button next to web role name and select entity permissions
\n\"portalparent2\"<\/a>
\n3. Click on Add Existing button and search for \u201cCustomer Service- Cases where contact\u2019s account is customer\u201d and select it.
\n4. If you will open this entity permission, you will see it is configure to allow access to case entity based on account scope, so contact can see cases of it\u2019s parent account.
\n\"portalparent3\"<\/a>
\nLet\u2019s see this in action now, let\u2019s say we have one portal contact and we have assigned our \u201cPortal Support User\u201d web role to this contact.
\n(Click on V sign next to contact -> select Web Roles-> Add Existing Web Role and select \u201cPortal Support User\u201d role.
\n\"portalparent4\"<\/a>
\nNow we can see in below screen we have one case for our customer HIMBAP where Arnav is primary contact
\n\"portalparent6\"<\/a>
\nNow we need to setup our entity permissions to access sub accounts.
\n5. Navigate to Portal->Security->Entity permissions->New. Let\u2019s call it \u201cAccess to Sub Account of the Parent Customer\u201d, we need to configure it like below:
\n\"portalparent7\"<\/a>
\nUsing this entity permission contact will have access to sub accounts of it\u2019s parent customer. Now to access cases we need to add a child entity permissions.
\n6. Navigate to Child Entity Permission sub grid and click on + sign
\n7. Click on Lookup control and select New under lookup control
\n8. Configure entity permissions like following:
\n\"portalparent8\"<\/a>
\nHere we are using Parent scope, to combine our parent and child entity permissions. Parent scope is used to access the entity which are not in a direct relationship.\u00a0Here contact is associated to\u00a0account, further account is\u00a0associated with sub accounts, whose cases we want to access.
\n\"portalparent9\"<\/a>
\nSo to access sub accounts cases we need to use Parent scope here. Now we need to add our \u201cAccess to Sub Accounts of the Parent Customer\u201d entity permission to existing Portal Support User web roles and when contact will access cases it will be able to see Cases from the sub accounts as well.<\/p>\n

\"portalparent10\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Requirement: Dynamics 365 Portal user should be able to access cases from it\u2019s parent customer as well as sub account of it\u2019s parent customer. Solution: We can implement this requirement using Web roles where we can configure entity permissions to access sub accounts and cases in dynamics 365 portal. We need two following entity permissions here: 1. Entity Permissions to… Read more »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[402],"tags":[506,503,504,505],"_links":{"self":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2947"}],"collection":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2947"}],"version-history":[{"count":6,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2947\/revisions"}],"predecessor-version":[{"id":2972,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2947\/revisions\/2972"}],"wp:attachment":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2947"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2947"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2947"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}