ISNA in Collabora Office: Detect Actual Unavailable-Value Errors

• Introduced: original Collabora release and launch date are not established by the sources reviewed.
• Availability: documented in Collabora Office 26.04 help, scoped to the desktop-help release.
• Platform scope: support in every online or mobile deployment is not inferred from desktop documentation.
• Checked: October 14, 2026. Direct function-specific documentation and independently derived examples; no native Collabora test was performed.

=ISNA(value)

value is a referenced value or an expression. Collabora identifies #N/A as the unavailable-value error tested by this function. Other errors do not become TRUE merely because they prevent a useful result.

The reference’s general sentence about errors returning FALSE is read alongside its explicit #N/A definition: the target #N/A class is the TRUE case, while another error such as division by zero is not. ISERROR is the broader predicate.

Examples use English function names and semicolon separators. Keep input, raw result and diagnostic flag in separate cells when practical.

Enter the following controls in A2:A7:

In B2 enter =ISNA(A2) and fill down. Expected flags are FALSE, FALSE, TRUE, FALSE, FALSE, FALSE.

A5 remains a failed calculation even though ISNA returns FALSE. The function asks one specific question about the error class; it is not a universal good-data check.

For the same source column:

=IF(ISNA(A2);"Unavailable";"Not an N/A error")

Filled down, only row 4 receives Unavailable. Every other row receives Not an N/A error, including the division-error row. This wording avoids presenting an unrelated error as a valid numeric observation.

If a reporting rule needs to distinguish both classes, test ISNA first and then ISERR for other errors. Keep any data-quality checks, such as allowed status values, separate from the error-type classification.

Create a clean lookup table in D1:E4 with headings Code and Quantity:

Put requests P01, P99, P02, P03 in G2:G5. In H2 enter and fill down:

=VLOOKUP(G2;$D$2:$E$4;2;FALSE())

The expected raw results are 8, #N/A, 0, 12. Then =ISNA(H2) filled down gives FALSE, TRUE, FALSE, FALSE. The explicit FALSE() requests an exact lookup; a sorted approximate lookup answers a different question.

The Collabora lookup reference documents the exact-match unavailable result used here. The keys contain no wildcard or regular-expression characters, avoiding an extra matching-mode assumption.

The clean table above contains no source errors, so P99’s #N/A identifies the absent key in that controlled setup. Now suppose a matched Quantity cell itself contains =NA(). Retrieving that value also yields #N/A, and ISNA returns TRUE even though the requested key exists.

Therefore, a general ISNA flag on a lookup does not prove “the key was not found.” It proves the result is an unavailable-value error. Preserve the matched source and lookup conditions if the report must distinguish missing keys from unavailable returned data.

IFNA supplies a fallback for #N/A, but the same interpretation caveat still applies. Replacing the raw result with a label does not identify its cause.

For H2:H5 from the clean table, map each result to a numeric indicator:

=IF(ISNA(H2);1;0)

Filled down, expected indicators are 0, 1, 0, 0, totaling 1. The legitimate zero quantity for P02 does not increase the unavailable count.

Keep the count range aligned with the request list. A missing source row, an unintended approximate match or an imported text code can change the meaning of a report without changing ISNA’s definition.

Inspect whether the cell is an actual error value or text that merely resembles one. Test NA(), a numeric zero and a deliberate non-N/A error before applying the rule to imported data.

The examples are independently calculated classifications based on the documented error scope and exact-lookup behavior. No native Collabora run, full error-rendering matrix or special-character lookup compatibility test is claimed.

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

Product-specific error classification comes from the direct Collabora help. Worked tables and helper results were independently checked. No native execution, full coercion matrix or broader client certification is asserted.