PlanMaker ISNUMBERP: Legacy Type Checks and Safe Replacement

• Introduced: Documented by the PlanMaker 2010 manual; the first introduction release is not established.
• Availability: Retained as a legacy compatibility function in the 2026 reference; no retirement or last-working-version endpoint is established.
• Scope: The current reference belongs to the 2026/NX manual family. Individual FreeOffice and mobile builds are not verified here.
• Checked: October 14, 2026, against the official function reference. Examples use vendor rules and independent calculations; no native PlanMaker test was performed.

=ISNUMBERP(Cell)

The current reference specifies one required cell argument. It returns TRUE for a cell containing a number or a logical value, and dates are considered numeric too.

The extra P is part of this historical function’s name. It is not an optional modifier on ISNUMBER. A direct replacement with ISNUMBER changes the result for TRUE and FALSE cells, which can change a downstream validation rule.

SoftMaker explicitly warns that ISNUMBERP does not exist in Excel. Saving a document in Excel format replaces calculations using it with their current result as a fixed value. A TRUE or FALSE displayed after export can therefore remain visible while the formula’s ability to recalculate is lost.

On a blank worksheet, enter Input, ISNUMBERP, ISNUMBER and ISLOGICAL in A1:D1. Prepare these cells:

The DATE reference documents the September 25, 2018 date construction. Date formatting can change its appearance without changing the date’s numeric type.

Enter =ISNUMBERP(A2) in B2, =ISNUMBER(A2) in C2 and =ISLOGICAL(A2) in D2. Fill B2:D2 through row 6.

The text, number, date and TRUE cases follow SoftMaker’s explicit examples and helper definitions. The FALSE case follows its rule that logical values qualify. Notice that the FALSE input still produces TRUE in ISNUMBERP: this function tests the input’s type, not whether the input itself is true.

If the intended modern rule is “accept numeric cells, including dates, but exclude logical values,” use ISNUMBER. It implements that documented distinction directly.

If a legacy rule intentionally accepts either numbers or logical values, the following explicit predicate models that choice for the ordinary cell types shown above:

=OR(ISNUMBER(A2),ISLOGICAL(A2))

Put this formula in E2 and fill to E6. The independently expected results are FALSE, TRUE, TRUE, TRUE, TRUE, matching column B for this dataset. In F2 enter =B2=E2 and fill through F6; the expected comparison results are all TRUE.

The ISLOGICAL entry identifies TRUE and FALSE as logical values. The OR entry returns TRUE when at least one supplied condition is TRUE.

This is a deliberate Boolean composition, not proof of identical behavior for every error cell, empty reference or imported type. Preserve representative tests before replacing formulas throughout a workbook.

The date row passes ISNUMBERP and ISNUMBER. That is consistent with PlanMaker’s documented type system, but it may be unsuitable for a column intended to contain only quantities or prices.

A type predicate does not establish that 42 is a valid quantity, that a date belongs in the expected period or that a logical value is meaningful to a calculation. Add the relevant range or data-validation rule separately instead of assuming a TRUE result certifies the entire record.

Similarly, the displayed word TRUE typed as text is conceptually different from a logical TRUE value. The example uses =TRUE() to create the intended logical value without relying on an imported string’s appearance.

The PlanMaker 2010 manual, page 511, already documents ISNUMBERP, its logical-value distinction, the recommended ISNUMBER replacement and fixed-value Excel export. It prints the argument label Value; the current entry uses Cell. The worked examples in both use cell references.

Those references establish historical and current documentation, not the first introduction release or a last supported version. ISNUMBERP is a retained legacy compatibility function with a recommended replacement, rather than a function proven retired from current PlanMaker.

Before exporting an editable workbook, preserve the original file, choose the intended acceptance rule and replace the legacy calls accordingly. Then change a sample input in the receiving application and confirm that its output actually recalculates. A saved Boolean result alone does not demonstrate a working formula.

The short entry does not give a complete blank, error-cell or text-to-number coercion matrix. Do not generalize the explicit ordinary-type examples to every imported value. Keep labels separate from numeric cells and inspect the actual formula rather than judging type solely by formatting.

Use PlanMaker’s formula-entry tools for local syntax. The important migration decision is whether logical cells should continue to qualify, not merely whether the replacement has a similar name.