Schema Formats
Excel
Excel mapping spreadsheets (.xlsx and .xls) — the common form an enterprise data team already maintains — are parsed into the MetaModel using a configurable column-to-attribute layout, with each ingest stamped to the ledger.
The Excel adapter recognizes both `.xlsx` (Office Open XML) and legacy `.xls` (BIFF) workbooks. Multiple sheets per workbook are supported, with each sheet either treated as a separate schema or combined into a single MetaModel under a configurable join column.
The column layout is configurable, not hard-coded. Most enterprise mapping spreadsheets already have a settled shape — `Source System | Source Table | Source Field | Target Table | Target Field | Transformation | Notes` — and the adapter accepts a column-mapping profile that names which column carries each role. Profiles are themselves versioned MetaModel artifacts.
Merged cells, formulas, and data validation rules are evaluated to their resolved values before the MetaModel is built. A formula that produces a target field name is captured both as the resolved name (for the MetaModel) and as the original formula text (as a `derivation_source` annotation), so a reviewer can prove which cell expression generated which mapping.
Each ingest writes a `SchemaIngested` entry with the importer module identifier (`ExcelImporter@x.y.z`), the SHA-256 of the workbook bytes, the column-mapping profile ULID in effect, and the assigned schema ULID. A reviewer can prove that the MetaModel was derived from a specific .xlsx file under a specific column profile.
Excel ingest is the entry point most enterprises use for the Mapping Import workflow — pulling a long-standing source-to-target spreadsheet into the governed MetaModel without re-keying. From that point forward, every edit writes `MappingDrafted` or `MappingRevised` to the ledger, and the spreadsheet stops being the source of truth.
The adapter never silently rounds or truncates numeric precision. `0.1 + 0.2`-style floating-point ambiguity in the spreadsheet is preserved exactly as Excel stored it, because round-trip fidelity is the point — the goal is auditability, not interpretation.
Audit ledger entries written by this capability
Each action in this capability appends one of the following entry types to the ULID‑keyed, SHA‑256 hash‑chained audit ledger. A reviewer can replay the chain to reconstruct exactly what happened, when, and under which role.
SchemaIngestedSchemaParsedColumnProfileAppliedSee excel demonstrated against your data
Pick a sample dataset or bring your own. We will walk the ledger from ingest through Approver release in a single working session.
Request a demoRelated across the platform
Where this capability hands off — upstream adapters, downstream governance, and the underlying audit primitives.