PlanMaker ISNONTEXT: Avoid mistaking non-text for numeric data

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.

=ISNONTEXT(Cell)

There is one required argument and no documented optional default. Use a single-cell reference such as A2 for the worked tests. The examples deliberately keep the inspected value in a visible source cell. 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.

SoftMaker describes ISNONTEXT as the counterpart of ISTEXT, including fixed strings and calculations returning strings. Create NontextControls with Entry, Nontext and Numeric in A1:C1. Enter these A values and fill B2 =ISNONTEXT(A2) and C2 =ISNUMBER(A2) through row 8.

The last row is an explicitly produced empty string. As a string result it is expected to fail the non-text test; it is not the same fixture as an empty worksheet cell. The Boolean rows demonstrate the important gap between “not text” and “numeric.”

Duplicate the sheet, then change A3 to numeric 84. Both B3 and C3 change to TRUE. Changing A3 to the comparison =2>1 instead would make B3 TRUE but C3 FALSE. The predicate classifies types; it does not determine whether an import conversion was meaningful.

Create QuantityTypes with Input, Not_text, Is_number and Action in A1:D1. Enter numeric 12, ="12", =2>1, numeric 0 and ="pending" in A2:A6. Fill B2 =ISNONTEXT(A2), C2 =ISNUMBER(A2) and D2 below through row 6:

=IF(ISNUMBER(A2),"Numeric input",IF(ISNONTEXT(A2),"Review non-text type","Review text"))

Expected actions are Numeric input, Review text, Review non-text type, Numeric input, Review text. Numeric zero is an accepted numeric type. The logical TRUE is non-text but is still sent for review. Whether negative or fractional numbers are allowed requires further business rules beyond this type audit.

In a copy, replace the numeric-looking string in A3 with numeric 12 after resolving its intended meaning. Its action changes to Numeric input. A4, containing a logical comparison, still needs review. A blanket acceptance based solely on B would have missed that distinction.

Fill E2 =IF(ISNUMBER(A2),0,1) through E6. The initial review count =SUM(E2:E6) is 3; after correcting A3 it is 2. This counts cells that are not numeric, not cells that are text. The distinction is visible in row 4.

The manual gives a concise type contract rather than a complete table for references to errors, cleared cells or specialized imported objects. This guide does not use those unresolved cases to promise a universal native truth table. Start with the supplied ordinary numbers, Booleans and strings before adding edge cases in your installation.

Do not use display formatting or alignment as evidence of the stored type. Formula results, imported CSV fields and text-looking numbers can be displayed similarly. Keep the source field and a separate audit column so a correction can be traced.

ISTEXT answers the opposite text question. ISNUMBER is the appropriate numeric-type check, while ISLOGICAL isolates Boolean values. None of these functions decides whether a quantity is plausible or whether a required value is present.

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.