Skip to content

Specialist format guide

Spreadsheet Formula and Hidden Sheet Review: Compare What Is Stored and Shown

Review SpreadsheetML sheets, formulas, cached values, hidden and veryHidden states, names, links, and calculation metadata before interpreting a workbook.

A spreadsheet can display a number while storing a formula, a stale cached value, or no cached value at all. A visible sheet can also depend on hidden or veryHidden sheets, defined names, external links, queries, or macros outside the visible grid. Open XML documentation distinguishes formula and value elements and identifies hidden worksheet states. This guide is a static package review, not a recalculation engine, workbook editor, privacy decision, or permission claim.

Updated

On this page

Inventory the package and every sheet state

Start with a neutral workbook ID, digest, package parts, workbook relationships, sheet names, relationship targets, visibility state, and defined names. The Microsoft Learn, (opens in a new tab) documentation describes worksheets as package parts containing cells, values, formulas, and characteristics. Record charts, tables, pivot caches, external links, queries, and macros as package-level objects even when the review does not inspect their contents.

Inventory the package and every sheet state (table)
Package fieldRecordStop if
Workbook identityNeutral ID and digestA derivative cannot be matched to source
Sheet relationshipName, relationship ID, target partTarget is missing or ambiguous
VisibilityVisible, hidden, or veryHiddenOnly the visible tab is inventoried
Defined namesName, scope, reference, and statusReference points to an external object
External linksRelationship and resolution stateReader follows a link automatically
Macros and queriesPresence and inspection stateBinary or query content is treated as absent

The hidden worksheet guide identifies Hidden and VeryHidden states. Preserve the exact state and package path. A hidden sheet is not necessarily sensitive, and a visible sheet is not necessarily complete.

Compare formulas with cached values and types

For each target cell, record address, cell type, formula text, cached value, shared-formula or array-formula context, style or number format, and whether a recalculation occurred. The Microsoft Learn, (opens in a new tab) documentation describes the formula and value elements, but a cached value reflects a prior calculation state. A workbook can therefore show a number without proving that it is current under a different reader or input set.

Compare formulas with cached values and types (table)
Cell evidenceRecordInterpretation boundary
FormulaExact text and reference scopeFormula text is not its evaluated result
Cached valuePresent, absent, type, and text withheld stateCached value may be stale
Cell typeNumber, string, boolean, error, or blankDisplay formatting is not storage type
DependenciesLocal, named, hidden, or external referencesCell reference is not a business definition
Error tokenExact token and locationError is not silently converted to blank
Calculation stateMode, chain state, and last known updateDate is not proof of recomputation

Synthetic formula fixture

Compare formulas with cached values and types code example, Plain text
<c r="B2"><f>A2*2</f><v>fixture-cached-value</v></c>
<c r="C2"><f>A2+Hidden!B4</f></c>
<!-- no real workbook values; review dependency and cache state -->

The fixture includes a cached value and a formula with a hidden-sheet reference but no private values. Record missing cached value as unknown, not zero. Do not evaluate a formula by substituting a guessed input.

Trace hidden dependencies, names, and links

A formula can depend on hidden or veryHidden sheets, defined names, tables, external links, volatile functions, data connections, or macros. Make those dependencies visible in the worksheet. The Microsoft Learn, (opens in a new tab) documentation supports inventorying hidden worksheet states; it does not say that opening a workbook exposes every dependency or that hidden content has a single meaning.

Trace hidden dependencies, names, and links (table)
DependencyRecordStop if
Hidden sheet cellSheet state, address, and referenceReference cannot be resolved
Defined nameWorkbook or sheet scope and formulaScope collision is unresolved
External linkTarget relationship and availabilityTarget is fetched without a boundary
Volatile functionFormula token and calculation stateReader behavior differs without evidence
Macro or queryPresence and inspection stateEffect is treated as a static value
Pivot or table objectSource range and refresh stateDisplayed result is assumed current

Keep formula references and business interpretation separate. A name such as Revenue is still a workbook token until its scope, formula, source range, and update behavior are documented. Do not publish a hidden value merely to prove a dependency exists.

Use calculation-chain evidence without overclaiming

The Microsoft Learn, (opens in a new tab) documentation describes the chain as the order in which cells were last calculated and explains that it is not a dependency tree and is not required. Record whether the chain exists, which cell references it contains, and whether a reader recalculated. If the chain is absent, do not assume that formulas were never evaluated or that the workbook is invalid.

Use calculation-chain evidence without overclaiming (table)
FindingDispositionNext action
Formula and cache presentConditionalRecord calculation state and inputs
Formula present, cache absentHold interpretationRequest controlled recalculation evidence
Hidden dependency unresolvedHoldInventory path without exposing values
External link or query presentRestrictedRecord boundary and refresh state
Calculation chain absentUnknownDo not infer validity or staleness
Workbook opens with repair warningHoldPreserve warning and package evidence

Stop conditions

  • Stop if formulas, cached values, and cell types cannot be distinguished in the package.
  • Stop if hidden or veryHidden sheets, defined names, external links, queries, or macros remain outside the inventory.
  • Stop if a reader recalculates or repairs the workbook without recording the resulting changes.
  • Stop if a cached value is treated as current without input and calculation-state evidence.
  • Stop before sharing private workbook content when the handling boundary or owner authority is unknown.

Close with a workbook packet and a qualified next step

Keep the package inventory, sheet states, formulas, cache states, dependencies, names, links, calculation evidence, and unresolved questions together. Pair this guide with the data provenance log for source and transformation history and the data card template for collection context. Spreadsheet structure is not a business-meaning, quality, privacy, or rights certificate.

For a supported non-health collection, after the owner has authority to describe the scope and a controlled workbook packet, the qualified appraisal request path may be a preparation step. It does not recalculate formulas, inspect hidden sheets, resolve links, create a quote, match a buyer, issue a legal opinion, or grant a license.

Takeaways

  • Inventory every sheet state and package relationship before reading the visible grid.
  • Keep formula text, cached value, cell type, and calculation state distinct.
  • Trace hidden sheets, defined names, external links, queries, and macros without exposing values.
  • Treat missing calculation-chain evidence as unknown, not as a pass or failure.

Sources

  1. Microsoft Learn: Working with Sheets (opens in a new tab)
  2. Microsoft Learn: Working with Formulas (opens in a new tab)
  3. Microsoft Learn: How to: Retrieve a List of the Hidden Worksheets in a Spreadsheet (opens in a new tab)
  4. Microsoft Learn: Working with the Calculation Chain (opens in a new tab)

Use the appraisal path after the workbook packet is organized.

It does not recalculate formulas, inspect hidden sheets, resolve links, create a quote, match a buyer, or grant a license.