ISNONTEXT in Collabora Office: Distinguish Nontext Values from Numeric Validation

• 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. Function-specific documentation and independently derived controls; no native Collabora test was performed.

=ISNONTEXT(value)

value is a referenced value or an expression. The source identifies numbers, text and logical values among the tested inputs. This is a text-type predicate, not a promise that the value can safely participate in an arbitrary numeric calculation.

ISNUMBER asks the narrower numeric question. ISTEXT identifies text directly. Choose the name that matches the intended requirement rather than using nontext as a synonym for number.

Prepare A2:A7 as follows:

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

The actual #N/A error in A5 is nontext under the documented rule. A literal string ="#N/A" would instead return FALSE because it is text. Similar-looking cell displays need not have the same type.

=ISNONTEXT(12/3)
=ISNONTEXT("4")

Expected results: TRUE and FALSE. The first expression produces numeric 4; the second supplies text. Both can be written inside formulas, so having a formula is not itself the criterion.

An empty text result is also text. The A6 control therefore returns FALSE even though it displays nothing. Use a separate emptiness rule when the task is to locate missing input cells.

Using the original control column, enter in C2 and fill down:

=IF(ISERROR(A2);"Error";IF(ISNONTEXT(A2);"Nontext value";"Text value"))

Expected labels are Nontext value, Text value, Nontext value, Error, Text value, Text value. ISERROR identifies the error first, rather than letting it blend into a broad nontext category.

The logical TRUE in A4 still receives Nontext value. If the next step specifically requires a measurement, test numeric type and the measurement’s allowed domain separately. Neither a Boolean flag nor an error should become an assumed quantity merely because it is not text.

Create numeric flags in two unused columns:

=IF(ISNONTEXT(A2);1;0)
=IF(ISTEXT(A2);1;0)

Filled down through row 7, the expected first sequence is 1, 0, 1, 1, 0, 0, totaling 3. The second is 0, 1, 0, 0, 1, 1, also totaling 3.

The two totals cover these six explicitly supplied controls. They do not establish every blank-reference, array or imported-error coercion rule across all Collabora clients. Preserve the controlled inputs when reproducing a migration test.

Suppose a quantity workflow receives numeric 8, logical TRUE and an NA() error. ISNONTEXT is expected to return TRUE for all three under the distinctions above. Only the first is the ordinary numeric measurement intended by this example.

A safer report keeps separate columns for error status, numeric status and any business rule, rather than reducing all validation to one nontext flag. For example, numeric zero may be an allowed quantity while a negative number may not be; those are additional rules that ISNONTEXT does not decide.

The type flag is still useful for profiling a mixed import. It helps reveal which values are represented as text, provided the report labels the result accurately and does not overinterpret it as readiness for arithmetic.

Use quoted text controls when you need to avoid automatic parsing differences. "8" and numeric 8 deliberately exercise different types; a display format that makes them look alike does not erase that distinction.

The reference explicitly establishes the error-returns-TRUE rule. This article does not infer every genuinely blank-cell behavior or native displayed error code from that statement. Examples are independently derived classifications, with unusual coercions and native application execution still unverified.

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

The direct product reference establishes the function definition and stated type/error distinctions. Worked controls were independently checked; native execution and broader client compatibility remain unverified.