Loading

Field Configuration and Templates

A browse view has no columns. Each record is drawn as a card from an HTML template, and the Field Configuration table decides which fields reach that template and what visitors can filter, search and sort on. This article covers both.

Where to find it

Architect Panel → Layout & Pages:

  • Browse Views — open a view in the Browse View Builder for its Field Configuration and Item Appearances cards

Field Configuration

One row per field in the datastore, with these columns:

  • Field Name and Field Type: which field this row is about.
  • Filter Mode: whether visitors can filter on it, and how (see Filters and Search Boxes).
  • Include in Search: whether the search box looks in this field. Offered for text fields only.
  • Sortable: whether it appears in the Sort By list. Offered for text, number and slider fields.
  • Show in Browse View: whether its value is sent to the page at all. It must be ticked for any field used in the List, Search or Map Pin template.

Field types that cannot be filtered, searched or sorted show "Not Available" in those columns. System fields such as the record's tenant are not listed.

Item Appearances

Three HTML templates, edited in code editors:

  • List: one card per record in the listing.
  • Search: one entry per result in the drop-down under the search box.
  • Map Pin: the card shown when a map pin is clicked. Empty means the List template is used.

Write a value into a template with a tag: ##AMDATA_, the field's row name, then ##, for example ##AMDATA_title##. The Placeholder Tags panel lists every tag: green tags are ready to use, red ones belong to fields not ticked Show in Browse View. ##AMDATA_ID## is always available. With location switched on, distance tags such as ##AMDATA_AMdistancetext## are added.

Writing a good List template

  1. Tick Show in Browse View for each field you need, and save.
  2. Start from a simple card: a heading for the title, one or two supporting lines, and a link.
  3. Cards sit inside a responsive grid row, so use column classes in your outer element to lay them out, for example three across on a desktop and one on a phone.
  4. Build the link to the record or a booking page from ##AMDATA_ID##. Cards do not link anywhere unless your template does.
  5. Save and check the view with real data, including records with empty fields.

Dropdown fields show their display text, not the stored ID. Values are inserted exactly as stored, so a field holding HTML is drawn as HTML: only show fields whose content you trust.

What goes wrong and how to tell

  • A card shows the tag itself (##AMDATA_venue##): the field is not ticked Show in Browse View, or the row name is misspelt.
  • Cards stack one per line on a desktop: the template's outer element has no column class.
  • Clicking a card does nothing: the template has no link.
  • A field you want to sort on is "Not Available": dates and dropdowns cannot be sorted; use a number or text field.

Worked example

A venue-hire catalogue ticks Show in Browse View for Name, Town, Capacity and Photo. The List template is a card in a column that is a third wide on desktops, with the photo, the name in bold, "##AMDATA_town## · up to ##AMDATA_capacity## people" beneath, and a "View details" link built from ##AMDATA_ID##. Capacity is Sortable, so visitors can choose "Capacity (High to Low)".

Recommendations

  • Send only what the cards show: unticked fields never leave the server.
  • Design for the empty field, so a missing value does not leave a stray label.
  • Keep the Search template short; it appears in a drop-down.
  • Use the Placeholder Tags panel rather than typing tags from memory.