Skip to content

Latest commit

 

History

History
73 lines (51 loc) · 3.13 KB

File metadata and controls

73 lines (51 loc) · 3.13 KB
title description author ms.author ms.topic ms.date ms.reviewer audience ms.search.region ms.search.validFrom
Using Microsoft Power Apps portals with the Party data model
Learn about the changes to the web roles for Microsoft Power Apps portals because of the party data model in dual-write.
RamaKrishnamoorthy
ramasri
article
03/22/2021
johnmichalak
IT Pro
global
2021-03-22

Using Microsoft Power Apps portals with the Party data model

[!INCLUDEbanner]

The Dual-write application orchestration solution version 2.0.999.0 and later includes data model changes to party and global address book for the Account and Contact tables. The changes allow many-to-many relationships that support advanced business scenarios. These changes are not supported by portal web roles, including the customer portal, that are shipped out-of-the-box or that existed in your environment before you installed dual-write. For the web roles to work as expected, you need to create new web roles by using the new data model.

In summary, the way the tables interact has changed, but the table permissions in the customer portal haven't changed. This article explains how to create new web roles that work with the new advanced data model.

This diagram shows the table relationship without the party and global address book data model:

without party model.

This diagram shows the table relationship with the party and global address book data model:

with party model.

Create a new table permission

To create these new table permissions, follow these steps:

  1. Sign in to Power Apps, and go to your apps.

  2. Select your Portal Management app.

  3. In the side bar, select Security > Table permissions.

    You must create three new permissions:

    • Contact to Party table connection
    • Party to Account table connection
    • Account to Order table connection
  4. Create and save a new permission for the Contact to Party connection, setting these parameters:

    • Name: Party to Account table connection (or your choice)
    • Table Name: msdyn_contactforparty
    • Website: Customer Portal
    • Scope: Contact
    • Privileges: Select all
    • Web roles: Authenticated Users, Customer Representative (or your choice)
  5. Create and save a new permission for the Party to Account connection, setting these parameters:

    • Name: Party to Account Connection (or your choice)
    • Table Name: account
    • Website: Customer Portal
    • Scope: Parent
    • Privileges: Select all
    • Parent Table Permission: Contact to Party Connection
  6. Create and save a new permission for the Account to Order connection, setting these parameters:

    • Name: Account to Order Connection (or your choice)
    • Table Name: salesorder
    • Website: Customer Portal
    • Scope: Parent
    • Privileges: Select all
    • Parent Table Permission: Party to Account Connection

[!INCLUDEfooter-include]