ISODD in Collabora Office: Odd Integer Parts, Negative Values and Pairing Rules

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

=ISODD(value)
=ISODD(33)
=ISODD(48)
=ISODD(-3.1)

The last three expected results are TRUE, FALSE and TRUE. The negative sign does not change odd/even parity, and the decimal part is discarded for the test.

Examples use English function names and semicolons in multiargument formulas. Expected results are independent numerical models of the product’s documented rule, not recorded native application output.

Enter these numbers in A2:A10 and fill =ISODD(A2) down B2:B10:

There are four TRUE flags. Notice that zero and magnitudes below one produce an even integer part, while 1.9 remains odd despite being close to two.

Rounding to the nearest integer before testing would answer a different question. Keep the chosen preprocessing rule visible when fractional measurements appear in a report.

=ISODD(-3.1)
=ISODD(INT(-3.1))

Expected results are TRUE and FALSE. INT produces -4, whose magnitude is even, while ISODD directly inspects magnitude 3 from the original input. The difference matters because the negative input has a fractional part.

See INT for the downward-rounding operation. Do not treat all “remove decimals” descriptions as the same algorithm.

For an already numeric control in A2:

=AND(A2>0;A2=INT(A2);ISODD(A2))

With inputs -3, 0, 1, 1.5, 2 and 3, expected flags are FALSE, FALSE, TRUE, FALSE, FALSE and TRUE. Only 1 and 3 satisfy all three conditions.

ISODD alone would accept -3 and 1.5 as well, because their integer magnitudes are odd. The sign and whole-number conditions define the required business domain; they are not built into ISODD.

This example assumes numeric inputs. It does not promise that AND suppresses every invalid argument or that a type check alone validates the intended meaning of a count.

Suppose independent groups contain 3, 5 and 8 items, and each group must form its own pairs. Fill this formula beside the counts:

=IF(ISODD(D2);1;0)

Expected unpaired counts are 1, 1 and 0, totaling 2 across the three separate groups.

Pooling all groups gives 3+5+8 = 16, which is even and has 0 unpaired items. Both calculations are correct for their stated rules; they describe different grouping policies. Do not add individual odd flags and assume that total is the remainder of the pooled sum.

For an explicit numeric sequence 1, 2, 3, 4, 5 and 6, evaluate:

=IF(ISODD(F2);"Group A";"Group B")

Expected labels alternate Group A, Group B, Group A, Group B, Group A and Group B. There are three labels of each kind.

The labels follow the supplied sequence values. If records are sorted, filtered or renumbered, decide whether the grouping should follow a stable identifier or the current displayed position. ISODD does not know which interpretation is intended.

ISEVEN supplies the opposite parity test for the same valid numeric controls. Neither predicate by itself confirms that a quantity is a nonnegative whole number.

Text-number conversion, Boolean/blank coercion, large-number precision and exact native error codes remain unverified here. Use ISNUMBER for a separate type inspection and retain simple positive, negative and fractional controls when moving a workbook to another client.

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

The complete function section was reviewed. Worked controls are independently checked expectations; native execution, broader client support and unlisted edge cases remain unverified.