Data tables and export

A table element lets you bind a collection (or a related-items field) to a grid on a page, choose which fields become columns, and let visitors or admins sort it and export it — no separate export step.

Adding a table

Drop a Table element onto a page and pick its data source: a collection, a filtered view of one, or a rollup field. Each column you add binds to one field on that data source, with:

• A header label you choose.
• A format — plain text, date, number, image, link, or yes/no — that controls how the value is displayed.
• An optional fixed width.

Turn on sortable to let visitors click a column header to sort by it. Rows use your site’s normal collection filters, so a table can be scoped the same way a repeater list can (for example, “only this edition’s entries”).

Export

Turn on CSV and/or XLSX export in the table’s settings, and an export button appears on the published page. Clicking it turns the table’s current rows — as displayed, respecting any sort or filter the visitor has applied — into a downloadable file, built entirely in the visitor’s browser. There is no separate export step or backend job.

Identity columns

Some columns reveal who submitted something — the submitter’s name or email. These columns only work on pages that are already restricted to signed-in members with a specific role; adding one to a public page is refused when you publish. This keeps a public comparison table from accidentally leaking who’s behind an entry, while still letting an admin page show exactly that.

Example

A members-only admin page (restricted to an admin role) has a table bound to the current festival edition’s entries, with columns for the participant’s name, email, submission period, and price. An Export button downloads the list as a spreadsheet — the payment sheet for that round.

A public page can bind the same underlying collection to its own table — say, a comparison of prices per period — just without the identity columns, since that page isn’t restricted to members.