dbt Core projects import every metric

A semantic_manifest.json written by dbt Core 1.12 or later now imports in full. Until now, its metrics that aggregate a column came in without that column: Axiome skipped them, along with the ratio, derived and cumulative metrics built on them — and a metric named like one of its table's columns could quietly aggregate that column instead.

What changed

• Every metric's expression is read. dbt Core and dbt Fusion write a simple metric's expression in different places. Axiome now reads both, so a dbt Core artifact imports exactly like the same project built with Fusion.
• History tables keep your joins. A project that models a dimension's history (an SCD2 table with validity dates) next to the dimension itself lost every join to that dimension on import. The joins now go to the dimension, and the history table still imports as plain dimensions.
• Clearer advice on an empty manifest. An empty semantic_manifest.json means a project still on the legacy YAML on dbt Fusion, but no semantic models at all on dbt Core — the import report and the docs now say which. If you migrate with dbt-autofix, check your percentile metrics afterwards: it drops their value.

Imported a dbt Core project before? Import it again, or let your next CI push do it — the preview shows which models change.

📖 Import from dbt · What gets imported