Power Platform Community Forum Thread Details

Need Evidence List to Filter by Multiple Companies per Contact

I am building a Power Pages site using the Enhanced Data Model and I have three Dataverse tables:

Company (customized Account table)
Contact
EvidenceCollection (320 checklist rows per Company)

Use Case:

Admin (Assessor) creates a Company record.
A Power Automate flow automatically creates 320 EvidenceCollection rows linked to that Company.
Admin creates Contacts, assigns them to Companies, and assigns a web role (Assessor or Customer).
A Customer belongs to only one Company.
An Assessor can belong to multiple Companies (many-to-many).

Expected Behavior

When a Contact logs into Power Pages:

If they are a Customer, they should see only the 320 EvidenceCollection rows for their Company (this works).
If they are an Assessor, they should see the combined EvidenceCollection rows for all Companies they are assigned to.

Example:

Contact = John Snow

Assigned Companies = 3

Expected Evidence rows = 3 × 320 = 960 rows in the list.

The Issue

Assessors only see EvidenceCollection rows for ONE company if we add them in one company if we add them in multiple companies they see nothing.

Question:

How can I configure Power Pages Table Permissions/Relationships so that a Contact associated with multiple Companies can see EvidenceCollection rows for ALL of those Companies?

Note:

This solution must be implemented without any JavaScript or Liquid code.

Only no-code / low-code (Dataverse relationships, Table Permissions, and Power Automate) can be used.

Categories:

General

For your Assessors you need to create a many-to-many relationship Between Contact & Account then add the Assessor contacts to the respective Accounts using that relationship.

Table permission for Account to Evidence create a Table Permission that is of Scope = Parent (in the designer these are called Child, in the Power Pages Management app they have Scope = Parent).

Table permissions for Assessor (contact) to Account create a Table Permission for the many-to-many relationship it will be either Scope = Parent or Scope = Contact (note, do not use Scope = Account as this scope only applies to the out of the box 1-to-many relationship for the parent account/company lookup on the contact table)

Table Permissions added to a Web Role the Assessors will use.

Quick Links