Contact

TRUE in Collabora Office: Create an Explicit Logical True Value

Logical Intermediate Collabora Office Calc

Use TRUE in Collabora Office for Boolean controls, conditional labels and reproducible logical tests without turning a constant into a data check.

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

Quick answer: TRUE() returns the logical value TRUE and takes no arguments. It is useful as an explicit Boolean control in a worksheet, but does not inspect data or prove that a condition has been satisfied.

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

=TRUE()

Keep the empty parentheses. The direct Collabora reference states that the function always returns logical TRUE. A quoted expression such as ="TRUE" instead produces text and is a different value type.

Examples use English names and semicolon argument separators. Where an input is meant to be Boolean, use the explicit function or a documented comparison rather than relying on a typed word being automatically interpreted in every locale.

Example 1: verify a positive logical control

=TRUE()
=NOT(TRUE())
=ISLOGICAL(TRUE())

Expected results: TRUE, FALSE and TRUE. NOT reverses the logical value. ISLOGICAL confirms its type.

The last result checks type rather than the truth of an external claim. ISLOGICAL(FALSE()) also returns TRUE because FALSE is itself a valid logical value.

Example 2: combine constants with ordinary conditions

=AND(TRUE();5>3)
=AND(TRUE();5<3)
=OR(TRUE();5<3)

Expected results: TRUE, FALSE and TRUE. TRUE does not force AND to pass a false condition, but a TRUE input is enough for OR to return TRUE.

AND requires every tested condition to be true; OR requires at least one. These controls make it easier to spot an incorrect logical connector before adding a more complex dataset.

Advanced example: use an explicit enable flag

Put =TRUE() in D1 and quantities 5, 0 and −2 in A2:A4. In B2 enter and fill down:

=IF(AND($D$1;A2>0);"Include";"Exclude")

Expected labels are Include, Exclude, Exclude. The fixed D1 reference applies the same enable flag to each row, while A2 advances to the next quantity.

Replace D1 with =FALSE() in this disposable control and the expected labels become Exclude, Exclude, Exclude. Restoring TRUE() enables the rule again, but only positive quantities qualify. The flag does not override the row-level quantity condition.

Keep the flag’s meaning visible in a nearby label. A permanent TRUE constant cannot certify that a person reviewed the data or that a separate approval exists; use an actual recorded process state when that distinction matters.

Advanced example: distinguish a constant from a comparison

=TRUE() remains TRUE regardless of whether A2 contains 5 or −2. By contrast, =A2>0 returns TRUE for 5 and FALSE for −2.

Use the constant when the intended input is an explicit logical value. Use the comparison when the value should depend on worksheet data. Replacing a failed comparison with TRUE() may make a report appear successful while removing the test it was meant to perform.

Text, labels and interpretation

=ISLOGICAL("TRUE") is expected to return FALSE because the quoted argument is text. That text may be an appropriate report label, but it should not be assumed to have the same type as the function result.

FALSE provides the matching negative logical control. Use both states when checking a conditional formula so a hard-coded output cannot pass every test unnoticed.

These examples use ordinary scalar logical inputs. They do not establish short-circuit evaluation that protects every dangerous nested expression, nor do they certify imported-text coercion across clients.

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.