Reference Another Workbook Safely in Gnumeric

A reference to another workbook is not the same as a reference to another sheet in the current file. Its success also depends on which workbook is loaded and which path identifies it. This exercise builds a small quote from a separate local price file, then checks whether the linked values actually change.

Scope: a source-qualified exercise, not a refresh guarantee

The syntax and boundaries below were checked against the official Gnumeric 1.12.62 manual and source on 2026-10-22. Scope is English, A1-style formulas in the GTK desktop application on Linux. No Gnumeric GUI, native external-reference calculation, save/reopen or relocation test was executed for this guide. The arithmetic is independently checked; the application results are expectations for you to verify.

The normal 1.12.62 formula resolver searches the application’s already-loaded workbooks. It tries a URI, an absolute filename, and a filename resolved relative to the referencing workbook’s location. That lookup does not open a closed source file. Therefore, save both files and keep them open in the same Gnumeric instance before entering references. Opening two separate Gnumeric processes is not equivalent. This is a source-derived prerequisite, not a promise that every import format follows the same rules. Resolver implementation.

Use only new synthetic practice files. There is no paired download here: portable links and fresh-opening behavior have not been established. If you only need separate tabs, use the simpler one-workbook summary workflow.

Create the two practice files

Create a local folder named reference-practice, with a subfolder named inputs. Use these two locations:

• reference-practice/inputs/Unit prices.gnumeric: the source workbook.
• reference-practice/quote.gnumeric: the report workbook.

In a new workbook, rename the first sheet Price list. Enter this table in A1:B4 and save it as Unit prices.gnumeric in the inputs folder. Leave other blank sheets unchanged.

Cell / row	A: Setting	B: Value
1	Setting	Value
2	Unit price	12.50
3	Shipping per order	4.00
4	Practice revision	1

The revision is a number you deliberately change during the test, not an automatic timestamp. Enter 12.50 and 4.00 as numeric values using your locale’s decimal separator. All amounts use the same unspecified currency units; this exercise excludes tax and discounts.

With that workbook still open, choose File → New to create another workbook in the same Gnumeric instance, rename its first sheet Quote, and save it as quote.gnumeric in the parent reference-practice folder. Saving first gives the relative path a known starting location.

Enter a filename, a sheet name and a cell address

Gnumeric’s documented pattern is =[filename]SheetName!CellAddress. The filename goes inside square brackets. A sheet name containing spaces is separately quoted, as in 'Price list'. The sheet name is required; the filename alone does not select a sheet. Cell-reference manual.

Enter these labels, input and formulas on Quote. Type the formulas separately if pasting the table inserts literal text.

Cell	Label in column A	Entry in column B
A1 / B1	Quote input or result	Value
A2 / B2	Quantity	8
A3 / B3	Linked unit price	=[inputs/Unit prices.gnumeric]'Price list'!$B$2
A4 / B4	Linked shipping	=[inputs/Unit prices.gnumeric]'Price list'!$B$3
A5 / B5	Linked practice revision	=[inputs/Unit prices.gnumeric]'Price list'!$B$4
A6 / B6	Order total	=B2*B3+B4

Read the B3 formula in four parts: inputs/Unit prices.gnumeric identifies the file relative to quote.gnumeric; 'Price list' identifies its sheet; ! separates the sheet from the address; $B$2 fixes the source cell when the formula is copied. Dollar signs lock the cell address, not the file location. See relative, absolute and mixed references for copying behavior.

Keep the filename’s spaces inside the brackets. Do not put Excel’s combined path-and-sheet quoting around this Gnumeric example. Gnumeric may rewrite the displayed reference using a relative URI or a full URI; inspect the actual destination rather than expecting its text to remain byte-for-byte identical. The reference formatter derives that representation from workbook locations.

Expected starting values are B3 = 12.50, B4 = 4, B5 = 1 and B6 = 104, because 8 × 12.50 + 4 = 104. Inspect B3:B6 in the formula entry area: a displayed total is not enough to establish that a formula, rather than pasted text or a fixed number, is present.

Check a real change, then restore it

Keep both workbooks open. In Unit prices.gnumeric, change Price list!B2 to 13.75 and B4 to 2. Return to Quote and check:

Check	Expected value
B3, linked price	13.75
B4, shipping	4
B5, linked revision	2
B6, total for eight units	114

If the report has not updated, activate its window and choose Edit → Recalculate, or F9, then check all four cells again. The manual explicitly warns that changes in another workbook may not be noticed automatically. The 1.12.62 action invokes workbook recalculation; it is not a command to reload the source file from disk. Recalculate documentation and action implementation.

For a second check, change Quote!B2 from 8 to 10 while the changed price is still 13.75. B6 should become 141.50: 10 × 13.75 + 4. Then restore Quote!B2 to 8, source B2 to 12.50 and source B4 to 1. Recalculate the report and verify 12.50, 4, 1 and 104 again. Save the source, then the report, after this restoration.

If a linked value is wrong, do not overwrite it with the expected number to make the exercise pass. Stop and inspect the source path, sheet and formula. The independent revision check helps distinguish the intended source from a different file containing the same starting price, but it is not a permanent audit trail or proof of freshness.

Understand what a local path means

The filename resolver supports these local path forms for an already-loaded workbook. These are alternative layouts, not extra files to create:

Text inside the brackets	Meaning relative to the saved report
Unit prices.gnumeric	Source in the report’s own directory
inputs/Unit prices.gnumeric	Source in its inputs subdirectory, as in this exercise
../prices/Unit prices.gnumeric	Source in a prices directory beside the report’s directory
/home/you/reference-practice/inputs/Unit prices.gnumeric	An illustrative absolute Linux filename; replace it with the actual path

A relative filename is relative to the referencing workbook, not an arbitrary shell working directory. An absolute filename identifies one machine’s location; it is not a portable link. This guide does not test Windows drive paths, network locations, cloud-sync behavior, symbolic links, URI escaping or shell abbreviations such as ~.

Moving the report alone, moving the source, renaming either file, or changing a sheet name can affect what the reference identifies or whether it resolves. Do not assume that Save As, moving a whole folder, or converting to XLSX/ODS will repair or preserve the relationship. Inspect the resulting formulas and run the changed-input check in the new location or receiving application. Use the file-format compatibility checks for conversion work.

Reopen safely: a separate acceptance test

A same-session change test does not establish successful reopening. Keep an untouched copy of the restored practice pair before testing the following sequence:

1. Save both files, close the report first, then close the source. Keep the source available at its recorded location.
2. In a fresh Gnumeric instance, open the source first. Use File → Open in that same instance to open the report second.
3. Check the actual source values, the report’s formulas and the four baseline results. Repeat the price-and-revision change test, then restore the inputs.
4. Record the application version, file locations, opening order and results. Treat this as verification of that pair in that environment only.

Do not use opening the report alone as evidence that Gnumeric fetched its source. In the native XML reader, an expression that fails to parse can be retained as a string expression after a warning. That source-code behavior is a reason to inspect formulas and change inputs, not a claim that a particular dialog or error was observed here. Native reader.

If the report opens incorrectly, close it without overwriting your known-good copy. Open the intended source first and retry from the untouched pair. Do not assume that opening the source afterward repairs expressions already read incorrectly. A displayed old number, no warning, or a successful save does not prove a live link.

Troubleshooting and sharing boundaries

• Filename or workbook is not recognized: confirm the exact saved path and that both files are loaded in the same Gnumeric instance. Check the subfolder spelling, brackets and required sheet name before changing anything else.
• The formula appears as text: inspect its leading =, cell format and any parse warning. Correct the reference on a practice copy with the source already open; do not merely hide the warning or replace the formula with a constant.
• The number looks plausible but is stale: change both the source price and revision, recalculate the report, and compare the linked cells individually. A source edited by another process on disk is not the same as the source currently loaded in Gnumeric; F9 is not a disk-refresh guarantee.
• It worked before moving or converting: return to the preserved original pair, identify the new source location and retest the changed inputs. No cross-format external-link compatibility is certified by this guide.
• You need to send only a final quote: a linked report can reveal source values and file paths. Share only the data you intend to disclose. Consider an explicitly labeled static output in a separate copy, verify its values and inspect remaining formulas; do not present a snapshot as a live report.

For important reporting, rely on a cross-file model only after its update, fresh-opening and distribution checks pass in your actual environment. Keeping related sheets in one workbook avoids this particular file-location dependency, although ordinary formula and data checks still apply.

Evidence and limits

Version-specific details were checked in the official Gnumeric 1.12.62 source archive, with its published checksum. The online manual is a convenient readable reference, not a guarantee that every paragraph matches every installed build. No native execution, application screenshot, automatic-refresh guarantee or portable downloadable workbook is claimed here.