Mutation proof
The requested cells, formulas, tables, or ranges contain the intended result.
Template preservation
Change the cells without casually rebuilding the package
Complex Excel templates contain relationships and package parts far beyond cell values. WolfXL modify mode targets supported edits while retaining unrelated source parts, subject to the published compatibility boundaries.
Where full rewrites become risky
Template-driven workbooks can combine pivots, slicers, charts, drawings, macros, external links, controls, protection, and cached formula results. A library may understand the requested cell edit while lacking full support for every surrounding package part.
openpyxl's own documentation warns that unsupported shapes can be lost when an existing file is opened and saved. That makes preservation an explicit workflow requirement rather than an incidental implementation detail.
WolfXL's bounded approach
- Inspect the workbook before mutation.
- Open existing OOXML workbooks in modify mode for supported targeted edits.
- Keep external links or VBA package parts when the selected workflow and options support them.
- Write to a new output path during validation.
- Compare the parts that must remain stable before production rollout.
Evidence required for a real workflow
Package proof
Relevant relationships and source parts remain present and structurally valid.
Consumer proof
The saved file opens and behaves correctly in the application or service that consumes it.
Start with the workbook inventory
Run the local scanner first, then compare each flagged feature with the compatibility matrix and known limitations. A clean inventory still requires a bounded save-and-open proof for the exact operation.
Turn one template into an acceptance contract
A Production Workbook Pilot defines the allowed mutation, required preservation checks, deployment environment, and recovery path before implementation begins.
Scope a preservation pilot