{"id":3325,"date":"2018-09-18T10:23:53","date_gmt":"2018-09-18T10:23:53","guid":{"rendered":"http:\/\/himbap.com\/blog\/?p=3325"},"modified":"2018-09-18T10:23:53","modified_gmt":"2018-09-18T10:23:53","slug":"access-entity-based-on-nn-relationship-for-dynamics-365-portal","status":"publish","type":"post","link":"https:\/\/himbap.com\/blog\/?p=3325","title":{"rendered":"Access Entity based on N:N relationship for Dynamics 365 Portal"},"content":{"rendered":"

Introduction<\/strong>
\nIn this article we are going to discuss how we can configure Dynamics 365 portal Web Roles and entity permission to access entity data based on the system N:N relationship. We are using Dynamics 365 trial and provisioned portal trial. Please refer our earlier article for setting up Dynamics 365 trial <\/a> if you want to setup a Dynamics 365 trial and you can refer this <\/a>KB to provision portal in your trial.<\/p>\n

Requirement<\/strong>
\nLet\u2019s say we have setup following custom N:N relationship between Account and Contact, so that multiple partner contacts can be associated to partner account and similarly partner account can be connected to multiple partner contacts.
\n\"partner1\"<\/a>
\nNow we need to configure entity permission so that current portal user (partner contact) can access all the associated partner accounts where he is either primary contact or a partner contact.<\/p>\n

Solution<\/strong>
\nWe can create a new web role or can use existing web role to set entity permissions. Let\u2019s create a new web role, navigate to Portal->Web Roles and Click on New.
\nLet\u2019s use \u201cPartner Portal User\u201d under name field and select your portal website, keep other field as default and hit Save.
\n\"partner2\"<\/a>
\nOnce it is saved click on V sign next to Partner Portal User web role and select entity permissions
\n\"partner3\"<\/a>
\nClick on New button to add entity permissions
\n\"partner4\"<\/a>
\nFill entity permission form like following and click on Save and Close, here we are using Contact scope and selecting our N:N relationship under Contact relationship.
\n\"partner5\"<\/a>
\nSimilarly we can setup another entity permission to allow access partner account based on the primary contact relationship like following
\n\"partner6\"<\/a>
\nNow let’s say we have added a portal user, Please refer our earlier article to add quick portal user<\/a>. Once contact is added we need to assign our web role to this portal user. Open contact and click on V sign and select Web Roles. Add our portal user web role by clicking on Add Existing Web Role<\/strong>.
\n\"partner11\"<\/a>
\nAdd this contact to any existing account as primary contact or create new account and set this contact as primary contact. Now when we navigate to portal with this new contact, we will be able to see one Account based on the primary contact relationship like following.
\n\"partner7\"<\/a>
\nLet’s go back to Dynamics 365 CE and open any Existing Account, let say Adventure Works associate current portal user to this account using N:N relationship. Now when we will go back to portal, we should be able to see two Customers like following.
\n\"partner9\"<\/a><\/p>\n

So this way we can configure entity permissions for 1:N and N:N relationship for Portal. Stay tuned for more Dynamics 365 Contents !!<\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction In this article we are going to discuss how we can configure Dynamics 365 portal Web Roles and entity permission to access entity data based on the system N:N relationship. We are using Dynamics 365 trial and provisioned portal trial. Please refer our earlier article for setting up Dynamics 365 trial if you want to setup a Dynamics 365… Read more »<\/a><\/p>\n","protected":false},"author":1,"featured_media":3206,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[402,522,508],"tags":[632,631,634,503,633],"_links":{"self":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3325"}],"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=3325"}],"version-history":[{"count":7,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3325\/revisions"}],"predecessor-version":[{"id":3343,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3325\/revisions\/3343"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/3206"}],"wp:attachment":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3325"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3325"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3325"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}