Contact

ERRORTYPE in Collabora Office: Read Native Collabora Error Codes from Cells

Information Intermediate Collabora Office Calc

Read Collabora native error numbers with ERRORTYPE, distinguish them from ERROR.TYPE categories, and build traceable diagnostic labels for error cells.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: If A1 displays Err:518, =ERRORTYPE(A1) has documented result 518. ERRORTYPE reads a native error number from a referenced error cell; it is distinct from the dotted ERROR.TYPE function.

Syntax and the reference requirement

=ERRORTYPE(Reference)

Reference is the address of the cell containing the error. The dedicated section describes a cell reference, not a text name of an error and not a complete list of accepted arbitrary expressions.

The help also says that selecting an error cell shows the predefined Collabora error code in the status bar. That gives a practical cross-check for a code read by the function. No status-bar or GUI inspection was performed for this guide.

Do not replace the referenced cell with a string such as "Err:518". A text label is not the underlying spreadsheet error value.

Example: reproduce the vendor’s conditional control

The reference explicitly states: if A1 displays Err:518, enter:

=ERRORTYPE(A1)

The expected number is 518. This is a documented conditional control, not an instruction to manufacture that error by guessing an invalid formula. If A1 already contains another error, its code is a different diagnostic case.

Keep the source error in A1 and the code in B1. Replacing A1 with its code would remove the original failing expression and make the issue harder to investigate.

Example: a division-by-zero diagnostic

Enter 10 in A3 and 0 in B3, then =A3/B3 in C3. In D3 use:

=ERRORTYPE(C3)

The Collabora ERROR.TYPE reference explicitly associates #DIV/0! with native Err:532. Combined with ERRORTYPE’s native-code purpose, the documentation-based expected D3 result is 532. This combined-source expectation has not been executed in Collabora.

By contrast, =ERROR.TYPE(C3) is documented to return the category number 2. Those results describe the same division-by-zero condition in two different coding systems. Do not remove the dot or treat the functions as aliases.

Guard a diagnostic column explicitly

The dedicated ERRORTYPE section does not provide a clear no-error return contract. Avoid relying on an undocumented result for successful cells. Use:

=IF(ISERROR(C3);ERRORTYPE(C3);"OK")

With the division-by-zero control, the documentation-based expectation is 532. After changing B3 to 2, C3 has independent result 5, and the guarded helper returns OK without requiring a no-error ERRORTYPE result.

ISERROR and IF provide the guard. The original calculation remains visible, and the diagnostic helper does not replace the business result with an unexplained number.

Advanced application: display a traceable message

Suppose D3 contains the guarded result above. A simple label can be built with:

=IF(D3="OK";"Calculation OK";"Native error code: "&D3)

The independent expected labels are Calculation OK for the successful control and Native error code: 532 for the division-by-zero control. This preserves the code without inventing an explanation for every error number.

If you maintain a separate code-description lookup, verify each description against the relevant Collabora reference. A copied list from another spreadsheet can mislabel the error, even when the displayed error text looks familiar.

Advanced audit: count recurring native codes

For a fixed helper list containing 532, OK, 518, 532, =COUNTIF(range;532) has independent result 2, where range is the actual helper range. COUNTIF can help prioritize repeated faults once the source cells and codes are retained.

A high count of the same code does not prove a single shared cause. Two divisions can fail because of unrelated missing or zero inputs. Use the code to locate candidates, then inspect their original formulas and dependencies.

Limits, troubleshooting, and file-format scope

The dedicated section establishes the Err:518 example and the general native-code purpose but does not comprehensively specify successful inputs, text coercion, arbitrary expressions, or every available code. Those cases are not certified here.

If the formula gives an unexpected result, verify that the referenced cell contains a real error and that you used ERRORTYPE without a dot. Compare the native code shown by the application, rather than confusing it with a small ERROR.TYPE category.

The vendor identifies ERRORTYPE as outside OpenDocument 1.3 OpenFormula, with namespace ORG.OPENOFFICE.ERRORTYPE. This extension identifier does not certify support or identical interpretation in another product. The supplementary ERROR.TYPE documentation used for the 532 mapping was also retrieved and reviewed on October 17, 2026.

Availability and verification

The exact function is documented in Collabora Office 26.04 desktop help, retrieved and reviewed on October 17, 2026. This establishes a documentation scope, not the first release that introduced the function or the last version in which it works; those versions and any retirement date remain unestablished. Collabora Online and mobile support are not inferred from desktop help, nor is behavior in another spreadsheet product.

The examples are documentation-based expectations with independent calculations. They have not been executed in Collabora Office. No application screenshot or native error/coercion certification is implied. Formulas use English function names and semicolon argument separators.

References