Skip to content

Related items

A rollup field shows items from another collection that reference the current one — without you copying or syncing anything. Point it at a collection and a reference field, and it lists the matches live, wherever the current item is displayed: in the CMS, in a member’s account area, or on a published page.

Add a field of type Related items to a collection, and configure:

  • From — the collection to look in (for example, Works).
  • Where — the reference field on that collection which points back at this one (for example, Works → Edition).
  • Group by (optional) — bucket the matches by another field on the matched items.
  • Limit — how many matched items to show (default 50, capped at 100).

The field always reflects the current state of the other collection — add, remove, or edit an item over there, and every rollup pointing at it updates on the next view. Nothing is stored on the item carrying the rollup field.

  • On a collection item in the CMS, as a read-only list of matches.
  • On a member’s account area, as “my [things]” pulled from a participation collection (see Recurring editions).
  • On a published page, bound into a repeater or a table like any other data source.

A “2026 Edition” item gets a rollup field named Entries, set to look in Works where Edition points back at it. Opening that edition in the CMS immediately shows every work submitted to it — no manual bookkeeping, and no risk of the list going stale.

A rollup looks one collection away — it can’t chain through a second rollup, and it can’t itself be used as a filter condition elsewhere. It is never a form input and never exported as if it were a stored column; treat it as a live view, not a value.