Skip to main content

Card View

The card view turns each returned row into its own card, listing the columns as label / value pairs. It is the most readable layout when a row has many columns, or when you want to look at records one at a time rather than scanning a wide table.

When to use cards​

  • A row has more columns than fit comfortably across the screen.
  • You are presenting a single record (for example one customer or one order).
  • You want a clean, mobile-friendly layout on a dashboard.

How it works​

Switch the result area to Cards and Kvery re-renders the current result set — no re-run required. Each row becomes a card; the column name is the label and the cell is the value. Paging works the same way as in the table view.

Controlling what appears​

Because cards are built from the same rows as the table, the same column modifiers apply:

  • Hide internal columns with ::hidden so they don't clutter the card.
  • Use ::json to pretty-print a column that holds JSON.
  • Use ::long / ::long-value for fields that contain longer text.
tip

Order your SELECT columns the way you want them to read on the card — Kvery preserves the column order from your SQL.