When to use
- Generated dashboards — status or inventory data produced by a scheduled job, where the page should always show the latest run.
- Data that changes faster than anyone edits — rows that would go stale in a hand-authored table.
For a table an author writes and maintains, use a table inside a Text block instead.
Key decisions
- Dataset is a name, not a URL: lowercase letters, digits and hyphens. The block fetches /api/status/<dataset> from the same site, so there is no endpoint, account or token to configure.
- The data describes itself: each dataset carries its columns, rows and wording. Authors choose the dataset and the title; the block decides how it looks.
- Freshness: each dataset states how old it may get before the table warns. Set Stale after (days) only to override that.
- Failures are visible: a dataset that cannot be read shows an error rather than an empty table, because an empty dashboard reads as "nothing has changed".
Example
The table below reads the news-releases dataset, the same one the EDS Platform News page uses.
All authoring options
General
dataset: dataset name, required. Lowercase letters, digits and hyphens, up to 41 characters
title: heading above the table. Empty for none
staleAfterDays: number. Empty uses the dataset's own threshold
Dataset contract
columns: label, field (dotted path into the row), renderer, labels, empty
renderer: text (default) | count | link | status
status: a fixed scale — ok | warn | alert | unknown — each with a glyph as well as a colour
freshness: semantic (generated | fetched), at, stale_after_days
Analytics
classes_track-inview: emit an event when the block scrolls into view
classes_track-link-click: emit an event when a link in the table is clicked
meta: block-level analytics meta, sent as a JSON string
Events emitted:
emu-data-table:inview
emu-data-table:link:click