ISLOGICAL in Collabora Office: Check Boolean Values Without Confusing False with Failure
Use ISLOGICAL to recognize TRUE and FALSE results, distinguish Boolean values from text and numbers, and validate a logical-flag column.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: ISLOGICAL returns TRUE when its input is a logical TRUE or FALSE value. Both =ISLOGICAL(TRUE()) and =ISLOGICAL(FALSE()) are expected to return TRUE. The second result is not a contradiction: the function checks type, not whether the input condition passed.
Availability and version history
- 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.
Syntax and the two levels of truth
=ISLOGICAL(value)
value is the value or expression to test. The official Collabora section defines logical TRUE and FALSE as qualifying values, and states that an error returns FALSE from ISLOGICAL.
There are two different questions: “Is this a logical value?” and “Is this logical value true?” ISLOGICAL answers the first. Keep that distinction explicit in labels and reports so a valid FALSE flag is not misclassified as malformed data.
Example 1: compare logical, numeric and textual controls
Prepare the following cells:
| Cell | Enter | Expected ISLOGICAL |
|---|---|---|
| A2 | =TRUE() |
TRUE |
| A3 | =FALSE() |
TRUE |
| A4 | numeric 99 | FALSE |
| A5 | ="TRUE" |
FALSE |
| A6 | ="FALSE" |
FALSE |
| A7 | =NA() |
FALSE |
In B2 enter =ISLOGICAL(A2) and fill down. Expected flags are TRUE, TRUE, FALSE, FALSE, FALSE, FALSE.
The quoted strings spell familiar logical words but remain text. Formula-generated text makes the distinction reproducible without relying on how an application parses manually typed TRUE in a particular locale.
Example 2: test comparison results
=ISLOGICAL(5>3)
=ISLOGICAL(5<3)
=ISLOGICAL(5=5)
Expected results: TRUE, TRUE and TRUE. The underlying comparisons return TRUE, FALSE and TRUE respectively, but all three results are logical values.
This is useful when a helper column should contain comparisons. ISLOGICAL can check the output type while a separate rule decides whether the actual comparison result permits a later step.
Advanced example: label malformed flags without rejecting valid false
For A2:A7, enter in C2 and fill down:
=IF(ISLOGICAL(A2);"Logical flag";"Review type")
Expected labels are Logical flag, Logical flag, Review type, Review type, Review type, Review type.
To inspect the value of a confirmed logical flag, use a second scalar conditional:
=IF(ISLOGICAL(A2);IF(A2;"Enabled";"Disabled");"Review type")
Expected labels are Enabled, Disabled, Review type, Review type, Review type, Review type. This is an ordinary scalar control, not a general guarantee about every array-evaluation context. Preserve the source values so the labels do not conceal why a row required review.
Advanced example: verify that an error predicate returns a Boolean
The Collabora reference specifically uses ISNA inside ISLOGICAL. Try:
=ISLOGICAL(ISNA(NA()))
=ISLOGICAL(ISNA(8))
Expected results: TRUE and TRUE. The inner ISNA results differ, but both are logical. ISNA identifies the unavailable-value error class; its result type is independently useful to check when composing a diagnostic formula.
This does not mean the original NA() input is logical. =ISLOGICAL(NA()) is expected to return FALSE. The outer function is examining whichever value the inner expression actually returns.
Advanced check: count valid logical entries
Map B2:B7 to numeric indicators in an unused column:
=IF(B2;1;0)
Expected indicators are 1, 1, 0, 0, 0, 0, totaling 2. That is a count of logical entries, not a count of enabled entries. Among the controlled valid logical values, one is enabled and one is disabled.
Explicit numeric mapping avoids assuming how a different aggregate handles Boolean values in a range. Keep the source and flag ranges aligned and exclude headers from a data-only count.
Troubleshooting and limits
An imported numeric code or text label may represent a Boolean concept in the source system without already being a logical value in the worksheet. Define the mapping deliberately rather than changing types until the screen looks right.
This guide uses explicit logical formulas, a documented numeric control, quoted words and a documented error case. Genuinely empty references, unusual numeric formatting and every import-coercion path remain outside the native evidence. The examples were independently checked, not run in Collabora.
References and verification
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.