ISEVEN in Collabora Office: Even Integers, Decimal Truncation and Count Validation
Apply Collabora ISEVEN with its documented decimal and sign rules, then distinguish parity testing from validation of nonnegative whole-number counts.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: ISEVEN(value) tests whether the integer part of a numeric value is even. The Collabora reference says fractional digits and the sign are ignored. Thus ISEVEN(-2.1) is TRUE and ISEVEN(3.999) is FALSE; the function is not a test that the original value was already an integer.
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. Complete function-specific documentation and independent controls; no native Collabora test was performed.
Syntax and primary controls
=ISEVEN(value)
=ISEVEN(48)
=ISEVEN(33)
=ISEVEN(0)
The last three controls have expected results TRUE, FALSE and TRUE. Zero is even under the documented example. A negative sign does not change the parity of the integer magnitude.
Examples use English function names and semicolons in multiargument helpers. All numerical expectations are independently calculated; no native Collabora run is claimed.
Example 1: inspect the truncation boundary
Enter these numeric values in A2:A11, then fill =ISEVEN(A2) down B2:B11:
| Input | Integer magnitude inspected | Expected ISEVEN |
|---|---|---|
| -3.9 | 3 | FALSE |
| -2.1 | 2 | TRUE |
| -0.9 | 0 | TRUE |
| 0 | 0 | TRUE |
| 0.9 | 0 | TRUE |
| 1.9 | 1 | FALSE |
| 2 | 2 | TRUE |
| 2.9 | 2 | TRUE |
| 3.999 | 3 | FALSE |
| 4 | 4 | TRUE |
Fractional values such as 0.9 and 2.9 can return TRUE even though the original inputs are not integers. There are seven TRUE flags in this ten-value fixture.
Example 2: negative truncation is not downward rounding
=ISEVEN(-2.1)
=ISEVEN(INT(-2.1))
Expected results are TRUE and FALSE. ISEVEN ignores the fractional part and sign, inspecting magnitude 2. INT rounds -2.1 downward to -3, whose magnitude is odd.
Ignoring fractional digits and rounding downward are not interchangeable operations for negative inputs.
Advanced example: validate a nonnegative even count
For an already numeric quantity in A2:
=AND(A2>=0;A2=INT(A2);ISEVEN(A2))
For inputs -2, 0, 2, 2.5 and 4, expected flags are FALSE, TRUE, TRUE, FALSE and TRUE. The first condition rejects negatives, the second requires a whole number, and the third checks even parity.
ISEVEN alone returns TRUE for every one of these five inputs because each has an even integer magnitude. The additional requirements are what reject -2 and 2.5. Keep this control limited to numeric inputs; it does not claim AND skips unsafe expressions or validates every error and text type.
Advanced example: identify an unpaired item
For nonnegative integer counts 0, 1, 2, 3, 4 and 5, ISEVEN returns TRUE, FALSE, TRUE, FALSE, TRUE and FALSE. If items must be grouped in pairs, use the explicit rule:
=IF(ISEVEN(D2);0;1)
The expected unpaired-item flags are 0, 1, 0, 1, 0 and 1. Their total is 3 across the six independent groups. This is not the number of unpaired items after pooling all groups: the pooled count 15 has only one remainder when grouped by two.
Whether groups may be pooled is part of the task definition, not something the parity function infers.
Advanced check: compare the complementary predicate
For the original ten numeric inputs, ISODD gives TRUE, FALSE, FALSE, FALSE, FALSE, TRUE, FALSE, FALSE, TRUE and FALSE, the opposite parity flags under the same documented truncation rule.
That complement relationship is demonstrated only for these valid numeric inputs. It does not certify that both functions accept every text, blank, logical or erroneous argument in the same way.
Limits and troubleshooting
Use ISNUMBER to inspect numeric type separately. A text label such as “2” may look like an even number, but its coercion is not established by this guide.
Very large values, exact binary boundaries, imported special types and every error code remain untested. Keep parity, integer validation and nonnegative-domain rules distinct, and use ordinary exact integer controls before applying the result to a real report.
References and verification
The complete function section was reviewed. Worked controls are independently checked expectations; native execution, broader client support and unlisted edge cases remain unverified.