Axi gets on with the modelling, and shows you what it changed

In Settings → Admin → Data, Axi used to stop and ask before doing what you had just asked for. It now puts the change in your draft straight away and tells you what it assumed — the draft is where you review it, and nothing is saved until you press Save model.

It does it, then you review

Ask for a description, a key, a measure or a metric and it is in your draft by the end of the answer. Axi says in one sentence what it assumed — paid orders only, created_at as the main date — so you can correct it, or take the whole batch back out with Discard. It still asks first when your request reads two ways, when it would replace a description you wrote, or when your data says otherwise.

Simple metrics land too. "Create a revenue metric" no longer comes back asking for a numerator, a formula or a window — those belong to ratio, derived and cumulative metrics, and a simple metric needs none of them.

Keys no longer wait for a save

A foreign key can now point at a primary key that is only in your draft. When orders.customer_id points at a customers table with no primary key yet, Axi checks both on your data and declares both in one batch — nothing to save in between.

The main date and the map

Two settings decide what a table can do in a chart: its main date, which every trend and date filter follows, and the geography of columns naming countries, states, regions or départements, without which no map can draw them. Axi now looks for both whenever it describes or sets up a table — it reads the values of a column before tagging it as geographic — and the empty window suggests Set this table's main date and Tag the geographic columns when the table you have open is missing them.

Find every change at a glance

Every row of the column list with unsaved changes now carries the blue dot the table tree already showed, whether Axi or you made the change — including on a collapsed group of nested fields. And the Axi window now opens at the bottom right, leaving the tree and its Save button in view.

Closing the Axi window no longer loses anything either: a request still in progress finishes and its changes land in your draft, as if the window had stayed open.

Metrics no longer wait for a save to show up. The Metrics entry of the rail counts unsaved metrics and carries the blue dot while one of them is unsaved, and a table's page lists the metrics stored on it — a metric is saved with its table, so this is what explains a table whose only change is a metric.

📖 Modelling with Axi · Keys are checked before they are declared · The proposal card