🎉 Celebrate with 10% OFF on All Products! Use Code: GFEX10 Or Buy Any 2+ Items for 30% OFF with Code: GFEX30!

Gravity Forms Combined Entries Premium Add-on Setup Guide

Updated 9 min read Gravity Forms Entries & Workflow
On this page
  1. Video walkthrough
  2. Requirements
  3. Installation
  4. Stacked or joined?
  5. Build a stacked view
  6. Map the columns
  7. Build a joined view
  8. Only entries where…
  9. Layout, search and order
  10. Who sees which entries
  11. Show the view on a page
  12. Look and Frontend Entry View
  13. Speed and large forms
  14. For developers
  15. Without a licence and uninstalling
  16. Frequently asked questions
  17. Can a visitor see entries of a form I did not add?
  18. Does it change my entries?
  19. Can I use the same form in several views?
  20. What if a field is renamed or deleted?
  21. Several Forms, One List

Video walkthrough

Gravity Forms Combined Entries: Show Entries From Several Forms in One List
Watch: combine Gravity Forms entries into one view, step by step. Watch on YouTube

The Gravity Forms Combined Entries Premium Add-on shows the entries of several Gravity Forms forms in one front-end view. You can stack the entries of up to six forms in one list with a Form column, or join them into one row per person by a shared field such as an e-mail address, the logged-in user or a member number. Fields that mean the same thing in each form go into one column, and visitors search, filter, sort and page through the combined list. This guide covers every setting.

A front-end page of the Riverbend Community Theatre showing one table with the entries of three forms: a search box, Form and Status drop-down filters, a submitted from and to date range and a Search button; Showing 1 to 10 of 18; columns Form, Name, Email, About, Status and Received with sortable headers; rows from Volunteers, Group bookings and Box office mixed newest first, for example Ethan Clarke from Volunteers, Ruth Adler from Group bookings and Oliver Grant from Box office; page links 1, 2 and Next
A stacked view: the entries of three forms in one list, newest first, with a Form column and filters.

Requirements

  • WordPress 6.5 or newer, PHP 7.4 or newer.
  • Gravity Forms 2.9 or newer (tested with 2.9 and 3.1).
  • An active licence key to add and change views. Published views keep working without one.
  • Optional: the GravityExtra Frontend Entry View add-on, for approving entries on the front end and a shared look. Combined Entries works without it.

Installation

  1. Upload the add-on zip in Plugins → Add New → Upload Plugin and activate it.
  2. Go to Forms → Settings → Combined Entries and enter your licence key.
  3. A Combined Entries menu appears below Forms for users who may read all Gravity Forms entries (administrators and roles with the Gravity Forms “view entries” right). Only these users can build views, because a view decides which entries are published.

Stacked or joined?

Stack the entries Join by a shared field
One row is one entry of any of the forms one entry of the first form
Good for enquiries from several contact forms, applications from several job forms, one archive of old and new versions of a form members and their bookings, applicants and their reviews, customers and their support requests
Form column yes, with your own name per form optional
Sorted by default date submitted, newest first date submitted of the first form

Both modes use the same columns, filters, visibility rules and layouts, so you can switch the mode later without starting again.

Build a stacked view

  1. Open Combined Entries → Add view and type a name, for example “All enquiries”. Visitors do not see this name.
  2. In 1. Forms keep Stack the entries and choose the first form. The next row appears as soon as you choose a form; you can add up to six.
  3. Type a short name in the view for each form, such as “Box office” instead of “Box office questions”. It is shown in the Form column and the Form filter. Empty means the form title.
  4. Leave Fill the columns from fields with the same label ticked and click Publish. The add-on creates a Form column and one column for every label that two or more forms share, for example Status.
  5. Now map the fields that have different labels (next section), choose the layout and who may see the view, and click Update.

Map the columns

The 2. Columns box has one row per column and one drop-down per form. In each drop-down choose the field of that form that fills the column. In the example the Name column shows the Name field of the box office form, the Contact person field of the group booking form and the Full name field of the volunteer form. A form without a matching field keeps “not shown”, and its rows get an empty cell in that column.

The Columns box of the view builder: one row per column with an order number and a label, then one drop-down per form (Box office, Group bookings, Volunteers) with the field that fills the column, for example Name, Contact person and Full name in the Name row, Email, Your e-mail and Email address in the Email row, and Search and Filter checkboxes; an Add a column button and the option to fill the columns from fields with the same label
Map the fields that mean the same thing in each form into one column.
  • Order: smaller numbers come first. Use steps of ten so you can slot a column in later.
  • Column label: the heading visitors see. Empty means the label of the first mapped field.
  • Form name: a special choice that shows the name of the form the row comes from.
  • Entry properties: Entry ID, Date submitted, Submitted by (the display name of the logged-in user who sent the form) and Approval status can be mapped like fields.
  • Search: the keyword box looks in these columns only. Hidden fields are never searched, so their values cannot be guessed through the search.
  • Filter: a drop-down above the list with the choices of the mapped fields. It works on drop-down, radio button and check box fields, on the approval status and on the form name. The choices of all mapped fields are merged, so “New” in two forms is one choice.
  • Remove: tick and update to delete a column. Add a column adds an empty row.

Password, credit card, file upload, hidden, HTML and admin-only fields are not offered and are never shown, even if someone edits the saved settings.

Build a joined view

Choose Join by a shared field in the Forms box. The first form is the main form: the view has one row for each of its entries. Every other form adds data to those rows.

  1. Choose the first form and its shared field, for example the Email field of the membership form.
  2. Choose the next form and its shared field, for example the E-mail address field of the season ticket form. Entries match when the values are equal; upper and lower case and extra spaces do not matter.
  3. If a form should match a different field of the first form, choose it under matches this field of the first form. In the example the volunteer hours form matches the hidden Member number field of the membership form instead of the e-mail address.
  4. Choose what happens to rows of the first form that have no match in every other form: Show them (empty cells) or Hide them.
  5. Map the columns as above. In a joined view a column can show fields of several forms; each cell shows the first form that has a value.
A front-end table of members joined with two other forms: columns Member, Membership, Member since, Package, Seats, Seating, Volunteer task and Hours; Ana Ruiz with Full season, 2 seats, Stalls, Ushering and 14 hours; Ben Okafor with only his membership; Clara Jensen with Pick three, Balcony, Costumes and 31 hours; Membership and Package filters above the table; Showing 1 to 8 of 8
A joined view: one row per member with the newest season ticket (matched by e-mail) and the volunteer hours (matched by member number).

Shared fields can be single line text, e-mail, number, drop down, radio buttons, phone, website, date and hidden fields, plus the entry ID and the user who submitted the entry. Joining by user is useful for member sites: everything a logged-in member sent in different forms ends up in one row. Entries sent by guests never match each other by user.

Several matching entries

When a joined form has more than one entry with the same value (a member bought two packages), the newest entry is used. To show every entry instead, use a stacked view of the two forms.

Only entries where…

Each form can have up to five fixed rules, for example “Status is not Closed” or “Group size greater than 20”. All rules of a form must match. Visitors cannot change them. Rules of a joined form decide which of its entries may be joined.

Layout, search and order

  • Table or Cards: cards use the first column as the title and show the other columns as label and value pairs, 1 to 4 cards per row (2 on tablets, 1 on phones). On phones the table turns into one box of label and value rows per entry.
  • Keyword box and date submitted from / to: switch them on or off. In joined views the dates are those of the first form.
  • Sorting: the default order and whether visitors may sort by clicking a column header (cards get a Sort by menu). Each form sorts by its own field, numbers as numbers, empty values last.
  • Entries per page: 1 to 100, with numbered page links and “Showing 1–10 of 18”.
  • Text when nothing is found: your own message for an empty search.

Search, filters, sorting and pages update the list without reloading the page. The address in the browser changes with them, so a filtered list can be bookmarked or shared, and the back button works. Without JavaScript the same links and the search form load the page normally.

Who sees which entries

  • Who can see the view: everyone, logged-in users only, or chosen roles. Other visitors see a short message (and a log-in link if they are logged out), never entry data.
  • Which entries: all entries, or only the entries the visitor submitted while logged in. This turns a view into a member portal: each member sees their own rows.
  • Approval: every entry, approved entries only, or approved entries plus the visitor’s own. The approval status is the one that the GravityExtra Frontend Entry View add-on sets with its Approve and Reject buttons.
  • CSV export: roles that get an Export CSV button. The file has the view columns and the current search, up to 10,000 rows, with a byte order mark for spreadsheets and values that look like formulas made safe.

In stacked views these rules apply to every form. In joined views they apply to the rows of the first form, and the joined forms add their data to the rows the visitor may see. Trashed and spam entries never show. Every rule runs on the server for the page, the AJAX updates and the CSV file.

Show the view on a page

  • Block: add the Combined Entries block and choose the view in its settings. The editor shows a live preview. Wide and full alignment are supported.
  • Show on page: choose a page in the side box of the view. The view is added below the content of that page; no block is needed.
  • Shortcode: the side box shows a shortcode with the view ID for classic content or page builders.

You can put several views on one page: each view keeps its own search, filters and page in the address.

Look and Frontend Entry View

Combined views take the fonts and colours of your theme. When the Frontend Entry View add-on is active, they also use its buttons, tables and colours, so both kinds of views look the same on your site. Choose Always use the own look in Forms → Settings → Combined Entries to turn that off. Designers can change the colours with CSS custom properties such as --gece-accent and --gece-radius.

Speed and large forms

The add-on reads the visible entry IDs of each form with one Gravity Forms query, the join and sort values with one indexed query per field, and then loads only the entries of the page that is shown. The combined list is cached for five minutes and rebuilt at once when an entry is added, changed, approved or deleted, or when a form or view changes. In our tests a view of three forms with 4,500 entries builds its list in well under a second. By default the newest 20,000 entries of each form are included; developers can change this with the gece_max_entries filter.

For developers

  • gece_max_entries: entries read per form (default 20,000).
  • gece_cache_ttl: cache time in seconds (default 300; 0 turns the cache off).
  • gece_export_max_rows: rows in a CSV file (default 10,000).
  • gece_page_view_class: class of the wrapper used by Show on page (default alignwide).
  • Request keys start with ce and the view ID, so several views can share a page.

Without a licence and uninstalling

Published views keep working when the licence is not active; adding and changing views needs an active licence. Forms → Settings → Uninstall removes the views and the add-on settings. Your forms and entries are never changed or deleted.

Frequently asked questions

Can a visitor see entries of a form I did not add?

No. A view reads only the forms you chose, only the columns you mapped, and only entries that match the visibility rules.

Does it change my entries?

No. Combined Entries only reads entries. Editing and approving stay in Gravity Forms or Frontend Entry View.

Can I use the same form in several views?

Yes. Each view has its own forms, columns and rules.

What if a field is renamed or deleted?

Labels you typed stay. A deleted field simply drops out of its column the next time the view is shown; the view keeps working.

Several Forms, One List

Stack or join the entries of up to six forms, map equal fields into one column and let visitors search, filter and sort the combined list.

Still need help?

Our support team answers tickets every day, usually within a few hours.

0
0
Your Cart
Your cart is emptyReturn to Shop
🔥 FREQUENTLY BOUGHT TOGETHER
Complete Combo & Save 40%!
ITEM IN YOUR CART
Gravity Forms Klaviyo Add-on
$39.00/yr
+
🎁 RECOMMENDED ADD-ON SAVE 40% OFF
Original Price: $39.00/yr
Bundle Special Price: $23.40/yr