Power Platform Community Forum Thread Details

Hi everyone! I have the following database structure.

1 Opportunity : N "Opportunity Accounts" (to link multiple children Accounts from the "Customer" to an Opportunity). For example, BIG ACCOUNT has 10 total children Accounts. A new Opportunity is created for BIG ACCOUNT where only three of its 10 children are related to the Opportunity.

Child Account A
Child Account B
Child Account C

Each of those children Accounts will have an Opportunity Account record for them tied to the Opportunity.

I then want to then show all Contacts that are associated with either Child Account A, Child Account B, or Child Account C in a gallery embedded on an Opportunity form.

Is this possible? I haven't had any luck with creating a formula for it.

Categories:

Building Power Apps

This is a classic N:N relationship filtering scenario in Dataverse, and you’re very close — you just need the correct relationship chain.

Your data model looks like this:

Opportunity
   ↓
Opportunity Account (intersect table)
   ↓
Account (child)
   ↓
Contact

What you want is:

Show all contacts belonging to the child accounts that are linked to the current opportunity.

✅ Recommended approach (works in model-driven apps)

You should not try to do this with FetchXML manually in the form or with JavaScript.

Dataverse already supports this using related tables + filtering.

✅ Step-by-step solution

1️⃣ Relationships required

You must have:

Opportunity → Opportunity Account
(1:N)
Opportunity Account → Account
(N:1)
Account → Contact
(1:N, standard relationship)

No custom logic required.

2️⃣ Create a Contact subgrid on Opportunity

On the Opportunity main form:

Insert Subgrid
Table: Contacts
View: any active contacts view

Now click Edit related records filtering.

3️⃣ Configure the relationship path

Choose:

Show only related records

Then select this chain:

Contact
  → Parent Customer (Account)
      → Opportunity Accounts
          → Opportunity

And set:

Opportunity = Current Opportunity

This tells Dataverse:

“Show contacts whose parent account is linked to this opportunity through the Opportunity Account table.”

4️⃣ Result

If your Opportunity has:

Child Account A
Child Account B
Child Account C

The subgrid will automatically show:

All contacts from Account A
All contacts from Account B
All contacts from Account C

No duplicates, no code, no flows.

✅ Why this works

Model-driven apps use relationship traversal, not joins you write manually.

Behind the scenes Dataverse generates FetchXML similar to:

Contact
 → Account
     → OpportunityAccount
         → Opportunity

You just define the relationship path once in the subgrid.

❌ What you should NOT do

❌ JavaScript filtering
❌ Custom FetchXML web resources
❌ Power Automate to copy contacts
❌ Duplicate contact records
❌ Rollup fields

All unnecessary.

⚠️ Important notes

✔ Contacts must use Account as Parent Customer

(Contacts linked only to Contacts or Leads will not appear.)

✔ Opportunity Account must be a proper intersect entity

(Not a lookup field stored on Opportunity.)

✔ Works with security trimming automatically.

✅ Final outcome

When users open the Opportunity:

They select child accounts via Opportunity Accounts
The embedded Contacts grid dynamically updates
Any contact added to those accounts automatically appears
No sync, no code, no maintenance

✅ This is the same pattern Microsoft uses for:

Opportunity Products
Quotes → Quote Lines
Account Teams
Access Teams

You’re modeling it correctly — you just needed the related-record filter path in the subgrid.

Community site session details

Filter Records In A Gallery Based On Multiple Related Records

✅ Recommended approach (works in model-driven apps)

✅ Step-by-step solution

1️⃣ Relationships required

2️⃣ Create a Contact subgrid on Opportunity

3️⃣ Configure the relationship path

4️⃣ Result

✅ Why this works

❌ What you should NOT do

⚠️ Important notes

✔ Contacts must use Account as Parent Customer

✔ Opportunity Account must be a proper intersect entity

✔ Works with security trimming automatically.

✅ Final outcome

✅ This is the same pattern Microsoft uses for:

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to the May Top 10 Community Leaders!

Leaderboard > Power Apps

Featured topics

Product updates

Community site session details

Filter Records In A Gallery Based On Multiple Related Records

✅ Recommended approach (works in model-driven apps)

✅ Step-by-step solution

1️⃣ Relationships required

2️⃣ Create a Contact subgrid on Opportunity

3️⃣ Configure the relationship path

4️⃣ Result

✅ Why this works

❌ What you should NOT do

⚠️ Important notes

✔ Contacts must use Account as Parent Customer

✔ Opportunity Account must be a proper intersect entity

✔ Works with security trimming automatically.

✅ Final outcome

✅ This is the same pattern Microsoft uses for:

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to the May Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Power Apps

Featured topics

Product updates