How to display entries from multiple forms in one view

Decide how the entries should appear. Use a join when two forms contain related information, such as a customer form and an order form, and you want matching records displayed in one row. The forms need a shared value such as an email address, reference number or customer ID.

Use a union when the forms collect similar records and you want to stack all entries into one list. A union does not require a shared field, but matching fields should use compatible formats if you want consistent columns.

Gravity Forms lets you review entries from the WordPress admin, but its standard Entries screen is centred on one selected form at a time. It does not provide a ready-made public page that combines several forms into one table.

If you only need an administrator export, exporting each form separately may be enough. For a public, searchable or editable view, plan on custom development or an additional view plugin.

For a custom solution, use the Gravity Forms PHP API and call GFAPI::get_entries() for the form IDs you need. Gravity Forms documents this method for retrieving entries with search criteria, sorting and paging, and its REST API can also request entries from multiple form IDs.

Then write a shortcode, block or template that combines the returned arrays, adds a form identifier to each record, sorts the combined results and outputs an HTML table. For a join, compare the shared field before rendering. For a union, map equivalent fields into the same columns and leave unavailable values blank.

Do not print entry values directly into the page. Escape output, restrict the view to the fields visitors should see, and check the current user before showing private submissions. If users can edit entries, add capability checks and validate every update.

Fetch entries in pages rather than loading the entire database. Gravity Forms documents paging for GFAPI::get_entries(); without it, a growing form can make the page slow or cause a timeout.

Test records that have no matching entry, duplicate shared values, blank fields, spam entries and a large number of submissions. A join can create multiple rows when one record matches several records in the other form, so confirm that this is what you want before publishing.

Also test the page while logged out. A view that works for an administrator may accidentally expose names, email addresses, payment details or other entry fields to everyone.

For most sites, install GravityView and its Multiple Forms extension, create a new View, choose the primary form and add a merge condition. Select Join to match related entries by one or more fields, or select Union to stack entries from multiple forms into one list. You can then add fields from each form, configure filters and publish the View on a page.

Enable strict entry matching when rows without a connected record should be hidden. GravityView is the quicker option when you need a maintained front-end table, search, filtering or front-end editing without writing and maintaining the data-query code yourself. Its documentation also lists limitations for some combined-form editing features, so test editing before promising it to users.