SHEET in Collabora Office: Identify a Worksheet Position from a Reference or Name

• Introduced: the original Collabora release and launch date are not established by the reviewed sources.
• Availability: documented in Collabora Office 26.04 desktop help.
• Platform scope: online and mobile deployment support is not inferred from the desktop documentation.
• Checked: October 14, 2026. Function-specific documentation and independent controls; no native Collabora execution.

=SHEET([Reference])

The optional argument can be a cell reference, area reference or sheet-name string. The dedicated help’s examples make results conditional on the actual sheet order; a name such as Sheet3 does not by itself establish position 3.

For the worked fixture, create three worksheets in this order:

1. Inputs
2. Summary
3. Archive

Use these exact simple names so the examples do not require unverified escaping rules for spaces, punctuation or apostrophes. English function names and semicolon separators follow the cited Calc help.

Enter these formulas in free cells on Summary:

The quotation marks make each argument a text sheet name. The function identifies that worksheet’s position rather than interpreting the word as a cell value or searching a column for matching text.

The numbers depend on the explicitly stated workbook order. They are not universal results for every file that happens to contain those names.

With the same sheet order, evaluate:

=SHEET(Inputs.A1)
=SHEET(Archive.C5)
=SHEET(Summary.B2:D4)

Expected results are 1, 3 and 2. The references identify which worksheet is involved. Changing the row or column within the same sheet does not change its sheet number.

The A1-style references use Collabora’s documented dot sheet separator. A cell’s contents do not determine the sheet number: Inputs.A1 can contain a number, a label or be empty without changing its worksheet identity in this fixture.

An area reference likewise belongs to the named sheet; SHEET does not count the area’s rows or columns.

Place =SHEET() in a free cell on Inputs and another copy on Archive. The expected results are 1 and 3. On Summary the same formula has expected result 2.

By contrast, =SHEET("Inputs") entered on Archive still identifies Inputs and gives 1. This contrast separates the formula’s location from an explicitly supplied target.

A template can use the omitted form as a structural diagnostic, but it should not be mistaken for a permanent business identifier. A sheet’s role might remain “input data” even when its position in the workbook changes.

Consider a separately saved copy of the fixture whose order is Archive, Inputs, Summary. Under the documented position meaning, the independently expected results become:

These are position-model expectations, not a captured native tab-reordering test. They explain why storing a sheet number as a permanent identifier can be fragile.

If a report depends on a particular logical worksheet, preserve a descriptive sheet name or explicit reference where appropriate rather than assuming “the second sheet” always represents the same purpose.

For Archive.C5 in the original fixture, SHEET identifies sheet 3, ROW identifies row 5, and COLUMN identifies column 3. Two equal numeric results here do not imply that sheet position and column position are the same kind of coordinate.

ADDRESS can construct address text when row, column and sheet-name components are known. SHEET itself does not return a sheet name, list all tabs or generate a complete address.

The short official section does not establish exact native behavior for nonexistent names, external documents, hidden-sheet counting, 3-D references or unusual sheet-name quoting. Those cases remain unverified rather than being assigned another spreadsheet’s error table.

Keep the workbook order alongside any expected SHEET outputs in a reproducible test. Without that setup, a result of 2 cannot be evaluated against an assumed name or role.

• Collabora Office 26.04: SHEET.
• Editorial testing standards.

Complete function-specific documentation reviewed. Worked outputs are independently modeled reference, text or arithmetic controls, not captured native application results. Unverified entry, conversion and error boundaries retain their stated scope.