PlanMaker ISODD: Find unpaired whole units and audit truncation

The PlanMaker 2026 reference, 2024 reference and 2021 reference were retrieved and compared on October 15, 2026. They document this function’s core operation. Documented by 2021 is not an original introduction date; the first introduction and any last-working-version endpoint remain unverified. The 2026/NX manual family does not establish per-build availability in FreeOffice, mobile clients or every operating system.

The examples below are vendor-supported controls and independently modeled expectations. No native PlanMaker execution, screenshot capture or workbook interchange test was performed. Keep the distinction between documentation support and observed application behavior when applying the guide to an installed version.

=ISODD(Number)

There is one required argument and no documented optional default. Number is the numeric value whose parity is tested. The documented decimal-removal rule is explained below. The formulas use English function names. The one-argument call needs no list separator; nested helper formulas below use commas, which may need adjustment for the installed locale.

The official controls are ISODD(1) and ISODD(1.75), both TRUE, and ISODD(2) and ISODD(2.75), both FALSE. The fractional part is discarded rather than rounded. That distinction matters for quantities and sequence numbers.

Create OddControls with Number, Odd and Even in A1:C1. Enter the following numbers in A and fill B2 =ISODD(A2) and C2 =ISEVEN(A2) through row 11.

A negative integer is odd or even according to its divisibility by two; the sign does not change that parity. The guide does not extrapolate the table into observed negative-fraction, numeric-text, blank or extreme-integer behavior.

Duplicate the sheet and change A4 from 1.75 to 2.25. B4 changes from TRUE to FALSE, and C4 from FALSE to TRUE. The original and changed values are both fractional; their parity flags describe only their retained integer parts.

Create PairRemainder with Quantity, Whole, Odd and Leftover in A1:D1. Enter 0,1,2,5,6,5.75 in A2:A7. Fill B2 =A2=TRUNC(A2) and C2 =ISODD(A2) through row 7. Put D2 below and fill downward:

=IF(B2,IF(C2,1,0),"Review fraction")

Expected B is TRUE, TRUE, TRUE, TRUE, TRUE, FALSE. Expected C is FALSE, TRUE, FALSE, TRUE, FALSE, TRUE. Expected D is 0,1,0,1,0,Review fraction. For these nonnegative whole quantities, a leftover of 1 means one unit remains after forming complete pairs. The fractional row is deliberately rejected even though ISODD returns TRUE.

For accepted whole rows, fill E2 =TRUNC(A2/2) only through E6. Expected complete-pair counts are 0,0,1,2,3. A reconciliation =2*E2+D2 copied through row 6 reproduces each original quantity. Do not extend this arithmetic to the text-valued Review fraction cell without a separate guard.

In a copy, change A7 from 5.75 to 5. Its leftover becomes 1, while the odd flag stays TRUE. After accepting the corrected whole input, =TRUNC(A7/2) gives 2 and 2*2+1=5. This illustrates why a passing parity test alone is insufficient.

ISODD is different from ODD, which is a rounding operation. Replacing a Boolean parity formula with a rounding function changes both the meaning and the result type. Keep the original quantity available during validation.

The whole-number comparison uses the documented TRUNC operation. It is not a promise that every imported decimal has exact intended precision; inspect rounding and input precision in the actual workbook. The sample quantities are intentionally small and explicit.

No optional argument or default is documented. The reference does not specify every text, error, array or maximum-width behavior. Use ISEVEN for the complementary numeric parity test, and test invalid input handling separately rather than borrowing another product’s error codes.

Record the PlanMaker version/build, edition, platform, language and workbook format. Recreate the original dataset, inspect the actual formulas and then apply the specified one-cell changes on a copy. Compare the original and changed outputs, not only a screenshot of the final values. Save/reopen and cross-product import results remain separate tests; neither was performed for this guide.