Nested Forms lets a Gravity Forms field hold an entire child form, so one parent submission can carry many child rows. Both live in gf_entry, with the perk storing the parent-child link as a comma-separated list of child entry IDs in gf_entry_meta on the parent. Useful for repeaters, team rosters, and order lines, but the Entries screen only shows nested rows when you open the parent entry one by one.

SleekView Charts treats gf_entry as the dataset and the nested field meta as the join. Count child entries per parent form, average rows per submission, group by the nested form's form_id, and split nested entries by field values stored in gf_entry_meta. Filters set at the view level cascade to every card so a date scope on parent entries also narrows the children.

Charts share the dataset with Table and Kanban modes, so flipping from a Bar of forms with the most nested rows to the actual child entries is one tab. On a site running team-signup or multi-line order forms, the same indexed gf_entry queries Gravity Forms already runs keep cards responsive without a separate reporting layer.

Nested Forms is the Gravity Forms perk that turns a single submission into an entire structured dataset. Teams use it for registrations with multiple attendees, orders with multiple line items, applications with multiple references. The data is rich.

Every parent entry carries a list of child entry IDs in postmeta, and each child holds its own field values, status, and date. Yet the Entries screen still shows nested rows only inside individual parent entries. Ops teams running a team-signup form want average team size, the largest rosters, and per-day nested volume.

Order admins want line-count distributions. Form admins want assurance that nested fields aren't sitting empty. None of these are exotic.

They are joins between rows the plugin already writes. SleekView Charts joins parent and child, treats them as one dataset, and turns nested forms from a hidden detail view into a real dashboard.