PlanMaker ISTEXT: Audit identifiers and text-producing formulas

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.

=ISTEXT(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.

The current PlanMaker reference explicitly includes both fixed strings and calculations returning strings. Create TextTypes with Entry, Text_flag and Nontext_flag in A1:C1. Fill B2 =ISTEXT(A2) and C2 =ISNONTEXT(A2) through row 9 after entering these controls:

Row 9 is an empty string result, not a truly cleared cell. Its expected classification follows the documented rule for string-producing calculations; it is an independent contract-based expectation, not an observed native result. The two predicates are documented counterparts for text classification.

Change A3 from ="42" to numeric 42 in a copy. B3 becomes FALSE and C3 TRUE, though the displayed characters may look unchanged. Formatting a number to resemble a code is different from storing a text identifier.

Create IdentifierAudit. Put Source in A1, Text_type in B1 and Review in C1. Enter ="0042", 42, ="A042", ="" and ="0043" in A2:A6. Fill B2 =ISTEXT(A2) and C2 =IF(ISTEXT(A2),"Text candidate","Review type") through row 6.

Expected B is TRUE, FALSE, TRUE, TRUE, TRUE. C labels every row except numeric 42 as Text candidate. That wording is deliberate: the empty string passes the type test, and the letter-containing code may or may not satisfy your identifier policy. ISTEXT does not validate required length, allowed characters, uniqueness or whether a field is populated.

If the source system says the second identifier is exactly four decimal digits with leading zeros, resolve that requirement before changing A3. In a controlled copy, replacing A3 with ="0042" changes its flag to TRUE while retaining the intended four-character identifier. Do not make that replacement merely because the numbers happen to match.

On a separate sheet enter the ordinary word North directly in A2 and the formula ="North" in A3. Fill B2 =ISTEXT(A2) and C2 =ISFORMULA(A2) through row 3. B is expected TRUE in both rows, while C is FALSE, TRUE. These cells hold the same text result but have different origins.

Replace the formula in A3 with the literal word North in a copy. The text flag remains TRUE while the formula flag becomes FALSE. Use this combination when an import should preserve formulas, not just visible values.

A TRUE result is not permission to run arithmetic on a text value. Parsing numeric text is a separate operation with locale-sensitive interpretation. Keep the original string when investigating an import, especially for identifiers, dates or currency labels.

Avoid using a multi-cell range as an assumed spill operation: the checked function page is cell-oriented. Native range handling, imported rich types, localized names and unusual errors are unverified. ISNONTEXT is the counterpart, while ISNUMBER narrows the test to numbers. ISFORMULA detects formula presence independently of the result type.

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.