ISTEXT in Collabora Office: Identify Text Values Without Judging Their Meaning

• 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.

=ISTEXT(value)

value can be a cell reference or an expression. The Collabora reference includes text, numbers, logical values and errors among the inputs to test, and explicitly states that an error produces FALSE.

ISTEXT does not determine whether a text value is useful, permitted or complete. A product code may properly be text, while a quantity stored as text may need review. Interpret the flag in the context of the column’s intended meaning.

Prepare the following control column in A2:A7. Use formula-generated text to avoid relying on automatic paste conversion.

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

An empty string is still text even though it displays no characters. An error value is different from text that spells an error code. For example, =ISTEXT("#N/A") is expected to return TRUE, while the NA() result in A7 returns FALSE.

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

Expected results: FALSE and TRUE. The first expression produces numeric 4; the second explicitly supplies text. A formula can therefore return either type, and the mere presence of a formula does not decide the ISTEXT result.

Use English function names and semicolon separators for multiargument helper formulas. Keep labels and output formulas outside the input range so the test does not alter its own source data.

Suppose the first three cells of a separate quantity column H2:H4 contain numeric 20, ="20" and numeric 0. In I2 enter and fill down:

=IF(ISTEXT(H2);"Text: review quantity";"Not text")

Expected labels are Not text, Text: review quantity, Not text. The middle entry deserves inspection because the column is meant to contain quantities.

Not text does not mean valid number. Logical values and errors also return FALSE from ISTEXT. For an actual numeric requirement, ISNUMBER is the more direct predicate. Add any sign, integer or unit rule separately.

Put ="00125" in K2 and numeric 125 in K3. ISTEXT returns TRUE for K2 and FALSE for K3. The first identifier retains its five-character textual representation, including leading zeros.

LEN applied to the controlled text K2 is expected to give 5. Converting K2 to a number merely to obtain a FALSE ISTEXT result would discard the identifier’s textual form. Decide whether the field is a code or a quantity before performing any conversion.

A display format can make numeric 125 appear with leading zeros, but appearance alone is not proof that its stored value is text. Preserve the actual source type when round-tripping an identifier through another file format.

For the original A2:A7 control, enter in C2 and fill down:

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

Expected indicators are 0, 1, 1, 1, 0, 0, totaling 3. The empty-string formula contributes because the question is text type, not visible character count.

ISNONTEXT answers the complementary type question for these explicit controls. Its TRUE results include logical and error values, so it should not be substituted for a numeric validation rule.

Check whether a surprising cell contains an actual text result, a displayed numeric format or an error. The direct source supports the ordinary type distinctions and error result used here. Genuinely empty references, unusual imported types and a complete coercion matrix have not been tested in native Collabora.

When the task concerns missing input rather than text type, consult ISBLANK and its separate documented rule that a cell containing a formula is not empty.

• Collabora Office 26.04: ISTEXT.
• 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.