Power Platform Community Forum Thread Details

Hello CU23100914-0 ,

Thanks for raising this question. I see you're running into issues displaying a subgrid within a Quick View form on your CustomEntity basic form in Power Pages—based on the screenshot, it looks like the subgrid (for child accounts) isn't rendering properly, and this is a common snag with nested Quick View setups.

This configuration isn't fully supported out-of-the-box in Power Pages the way it works in model-driven apps, as Quick View forms are designed for simple, read-only summaries and don't natively carry over embedded subgrids due to how the portal renders nested data. Instead, subgrids in Power Pages require explicit configuration via Basic Form Metadata on the main form, and Quick View subgrids often fail to load or show errors because of permission scoping and relationship depth limits.

1.Add a Direct Subgrid to the Main CustomEntity Form (Recommended)

Instead of relying on the Quick View, embed a read-only subgrid directly on your CustomEntity basic form to show related accounts from the lookup.
Steps:
In Power Apps maker portal, go to Solutions > your solution > Tables > CustomEntity > Forms > open the main form used for Power Pages.
In the form designer, select the section where you want the subgrid (e.g., below the Account lookup field).
From the Components pane, drag a Subgrid into the section.
In subgrid properties: Set Data source to "Related records only," select Account as the table (via the N:1 relationship from CustomEntity to Account? Wait—no: for child accounts of the selected Account, use the lookup to filter: set the relationship to Account's child records, like accounts under a parent account if that's your setup; otherwise, use a view filtered by the parent Account ID).
Choose a view (e.g., "Active Accounts") and set max rows (e.g., 5-10 for performance).
Save, publish the form, then in Power Pages design studio: Edit your CustomEntity page > select the form component > ensure it uses this updated form.
In Portal Management app: Go to Content > Basic Form Metadata for CustomEntity > add a new record with Type: Subgrid, enter the subgrid's Name (from form designer properties), and configure basic settings like View Actions (e.g., enable Details for read-only viewing).
This displays child accounts tied to the Account lookup value once the form loads (works for Edit/Update views, not Create if no parent record exists yet).
Permissions: Ensure portal users have Read on Account table via Table Permissions in Portal Management.

2. Use a Separate List Component on the Page

Place a standalone List component next to or below your CustomEntity form to show related child accounts, filtered by the Account lookup.
Steps:
- In Power Pages design studio: Edit the page > add a List component > connect to Account table.
- In list properties: Select a view filtered for child records (create a custom view in Power Apps: e.g., "Child Accounts" where Parent Account equals the dynamic Account ID from the form).
To link it dynamically: Use the page's URL parameters or FetchXML in the list config to filter by the CustomEntity's Account lookup (e.g., pass Account ID via query string on form load).[ from previous, but general]
For interactivity: Enable Details action in list metadata to open child accounts in read-only forms.
This isn't nested in the form but provides a clean, OOB way to show related data without Quick View issues. It's performant and supports pagination if you have many children.

3. Simplify the Quick View (Fallback for Basic Display)

If you must use Quick View for the Account lookup, strip out the subgrid from the Account's Quick View form and add key child account fields or a summary (e.g., a calculated field counting child accounts).
Steps:
- Edit Account's Quick View form: Remove the subgrid > add fields like "Number of Child Accounts" (roll-up or calculated column).
- On CustomEntity form: Keep the Quick View for Account, and pair it with option 1 or 2 above for the full child list.
This avoids the error but doesn't show the actual subgrid—use it if read-only summary suffices.

Testing and Troubleshooting

Preview in Power Pages design studio after changes—ensure the form is saved/published and synced.
Check browser console (F12) for errors like permission denials or relationship issues; common fix is verifying Table Permissions for Read on child records.
If child accounts don't filter correctly, confirm the relationship (e.g., Account as parent to child accounts via a lookup field on child records).
For Create forms, subgrids won't show until the record is saved—use Edit forms for testing.

These OOB methods should resolve the error while keeping things simple and aligned with Power Pages best practices. Kindly follow the steps and share your feedback.

Best Regards,
Jerald Felix

Community site session details

Display subgrid in quick view on the basic form

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Chiara Carbone – Community Spotlight

Congratulations to the October Top 10 Community Leaders!

Leaderboard > Power Pages

Featured topics

Product updates