PlanMaker ISNA: Track unavailable inputs through dependent calculations
ISNA identifies the actual #N/A error. It does not search text for the characters N/A, and it does not regard a genuine numeric zero as unavailable. A dependent formula can also contain #N/A after using a missing source.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
ISNA identifies the actual #N/A error. It does not search text for the characters N/A, and it does not regard a genuine numeric zero as unavailable. A dependent formula can also contain #N/A after using a missing source.
Availability and verification
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.
Syntax and argument
=ISNA(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.
Recreate the vendor propagation example
SoftMaker describes a source cell containing =NA() and another cell that multiplies it by two. Reproduce it on MissingControl: put =NA() in A1, =A1*2 in C7, =ISNA(A1) in E1 and =ISNA(C7) in E7. Both flags are expected to be TRUE. The error can travel beyond the cell where the missing marker was first entered.
In a copy, change A1 to numeric 6. C7 becomes 12 and both flags become FALSE. This checks dependency propagation rather than only a standalone NA literal. Some older English help prose uses the spelling NV in its narrative; the checked English signature and current reference use NA().
A complete price-availability worksheet
Create PriceAvailability with Price, Quantity, Amount and Missing_price in A1:D1. Enter A:B below. Fill C2 =A2*B2 and D2 =ISNA(A2) through row 8.
| Row | A price entry | B quantity | Expected C | Expected D |
|---|---|---|---|---|
| 2 | 12 |
3 | 36 | FALSE |
| 3 | =NA() |
2 | #N/A | TRUE |
| 4 | 0 |
4 | 0 | FALSE |
| 5 | 17 |
1 | 17 | FALSE |
| 6 | =NA() |
3 | #N/A | TRUE |
| 7 | 5 |
5 | 25 | FALSE |
| 8 | 9 |
2 | 18 | FALSE |
The known amounts sum independently to 96, but that is an incomplete subtotal, not the full order value. Keep both missing rows visible. The zero-price row is known and contributes zero; it must not be relabeled missing simply because its amount is also zero.
Advanced: a completeness count alongside the calculation
Fill E2 =IF(ISNA(A2),1,0) through E8. =SUM(E2:E8) is expected to return 2. Separately fill F2 =ISNA(C2) through F8; it has the same TRUE pattern for this numeric-quantity dataset because each missing price propagates to the corresponding multiplication.
Duplicate the sheet and replace A3 with 7 and A6 with 8. The changed amounts are 14 and 24. E totals 0, and =SUM(C2:C8) is now expected to be 134. That full total reconciles with the previous known subtotal: 96+14+24=134. The source prices and quantities remain available to explain the difference.
On another control sheet, enter ="#N/A", 0 and =1/0 in A2:A4, then fill B2 =ISNA(A2) downward. All three flags are expected to be FALSE: text, zero and an unrelated error are not the specific missing error. Use ISERROR if any failure should be flagged.
Troubleshooting and scope
A TRUE result tells you the category, not why it arose. A lookup that failed to find a match and an intentional NA marker may need different treatment. Inspect the source formula before replacing the result.
Do not use ISNA(A2)=FALSE as proof that A2 is numeric or complete for your business purpose. Text and other errors pass that narrow test. ISNUMBER checks a different property, and ISERROR covers all errors.
These examples use single-cell references. Array broadcasting, unusual imported types, exact localized error displays and cross-product recalculation are not established here. IFNA can supply a fallback, but a zero fallback should never silently convert an unavailable price into a free item.
Verification checklist for your installation
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.