A balance now sits beside metrics from any other table. MRR, stock on hand, an account balance — any measure read at the last (or first) value of each period — used to be refused next to a metric from another table. It now shares a chart or a table with them, grouped by the fields they share.
BigQuery sources that write one table per day — GA4's export, with events_20260101, events_20260102 and so on — now show up as one table, events_*, the name BigQuery queries them by. Until now each day was a table of its own: a year of GA4 meant 365 identical tables in the semantic layer, and a connection slow to create and slow to load.
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.
Axi answered about the table you had open, because that was the only thing it could be told about. A picker above the message box now says what it is looking at — This table, or Whole connection — and a sweep no longer needs you to type "continue".
Axi could describe your tables and declare their keys. It can now write the two things you actually build dashboards on — measures with their business rule baked in, and metrics — and it checks a metric against the engine before offering it to you.
Axi could describe the table in front of you. It can now work through the whole connection — and the left rail saves the result in one press.
Axi could already put a key in your draft. It now reads your data first, and shows you the count it read.
Axi could already explain your semantic model. It can now change it — by putting the change in your draft, where your own edits live, and leaving Save model to you.
The Check card on a metric's page told you the definition compiles. It now also tells you the number: Run executes the metric — unsaved edits included — and shows its value over the last 30 days.
On a BigQuery connection, the table page in Settings → Admin → Data now shows nested fields as rows of their own and keeps flatten models next to the table they come from.