Named Ranges and Tables

Named references let formulas describe intent instead of coordinates.

Why they matter

• Revenue_Q1 is easier to audit than Sheet1!B2:B100.
• Table-style references stay meaningful as data grows.
• Names can centralize workbook assumptions.

Common usage patterns

• Use workbook-level names for constants and key ranges.
• Use table columns for row-wise calculations.
• Keep naming conventions consistent across teams and bindings.

Short example

Name: TaxRate = 0.0825
A2 formula: =A1 * TaxRate

Related

• Dependency Graph and Recalculation
• Custom Functions (Rust, Python, JS)
• WASM Plugins: Inspect, Attach, Bind

Scope rules

Named ranges can be workbook-scoped (visible everywhere) or sheet-scoped (visible only within that sheet). When both exist with the same name, sheet-scoped names take precedence within their sheet. The engine resolves names during reference binding, before evaluation.

Structured table references

Structured table references (e.g., Table1[Column], Table1[@Column]) are recognized by the parser. The full-v0 SheetPort profile reserves native table selector support. Currently, layout-based selectors provide equivalent functionality for SheetPort manifests.