Contact
12 programs
Explore the site

IFNA in SoftMaker PlanMaker: Handle Missing Lookup Values

Logical Intermediate SoftMaker PlanMaker 2026

Use PlanMaker IFNA to replace only the #N/A error, with example data, comparison to IFERROR, official syntax and compatibility notes.

Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in SoftMaker PlanMaker 2026. How formula examples are checked

IFNA is useful when a lookup, import or reference may not have a value yet, but errors such as division by zero should remain visible so someone can correct them.

Official English syntax and argument meanings

SoftMaker uses the parameter labels Cell and Value for IFNA:

=IFNA(Cell, Value)
Argument Required Meaning Default
Cell Yes A referenced cell whose content (including an error) should normally be returned. This guide uses explicit references such as D2, matching the vendor example. None.

A valid number or text value passes through unchanged. A genuine #N/A error selects the second argument. Other error types remain errors. Do not confuse the actual #N/A error with plain text typed as "#N/A" (the latter is a text string, not the error), or with a blank cell (a blank is not automatically #N/A).

The examples reproduce the comma separators in the English vendor syntax. For a regionally configured installation, check the Formula → Function dialog and the application’s number separator settings rather than guessing punctuation. A leading = is required in a cell formula. This was checked from documentation, not by native keyboard entry.

Reproducible sample worksheet

Enter the following table into a new worksheet. The status formulas in column D deliberately create two different error types.

Row A: Item B: Delivered C: Ordered D: Calculated status
2 Pens 8 10 =NA()
3 Paper 6 0 =B3/C3
4 Tape 12 12 =B4/C4
5 Clips 3 5 =NA()
6 Folders 0 4 =B6/C6

NA() is itself an officially documented PlanMaker function that intentionally produces an error value #N/A; it is more reproducible than asking you to paste an unknown cell error. Official PlanMaker 2026 NA documentation.

Example 1: mark unavailable data clearly

  1. Enter =NA() in D2 and confirm. The expected result in that source cell is the error #N/A.

  2. Enter this function into E2:

    =IFNA(D2,"Pending source")

Example 2: preserve an unrelated calculation error

  1. Enter =B3/C3 in D3. With 6 delivered and 0 ordered, the underlying expression is division by zero.
  2. Expected D3: #DIV/0!. Expected E3: #DIV/0!. IFNA does not replace this error because it is not #N/A.
  3. Fix the invalid denominator (or handle it under a separately documented rule) rather than masking it as a missing lookup.

The error names and their meanings are documented in PlanMaker 2026’s error-value list.

Example 3: keep successful data unchanged

Cell Actual D-cell expression Expected D-cell result Expected E-cell result
E3 =6/0 #DIV/0! #DIV/0! (still visible)
E4 =12/12 1 1
E6 =0/4 0 0

Valid 0 and valid 1 pass through; IFNA is not a numeric threshold test.

Advanced application: distinguish missing lookups from broken calculations

Suppose a daily import supplies a numeric result in column D. Mark missing records as =NA() until the import is complete. Put this formula in an adjacent display column:

=IFNA(D2,"Awaiting import")

Expected result for row 2: Awaiting import. When D4=1, changing the formula reference to D4 returns expected 1. If an import writes an invalid formula that returns #DIV/0!, IFNA deliberately exposes it rather than labeling it a missing record.

If the reporting policy explicitly needs to replace any remaining error, you can layer the two documented functions:

=IFERROR(IFNA(D3,"Awaiting import"),"Other calculation error")

Expected result for row 3: Other calculation error. Reason: the inner IFNA does not intercept #DIV/0!, whereas the outer IFERROR replaces any error. This is an independent logical evaluation of the documented functions, not a native test of nested evaluation in PlanMaker. Prefer the simpler IFNA formula whenever preserving distinct error types matters.

Troubleshooting and mistakes to avoid

Observation Interpretation or correction
IFNA did not hide #DIV/0! or #REF! This is intentional. IFNA catches #N/A only. Use IFERROR only if your policy permits masking all errors.
Expected a fallback for a blank cell A blank cell is not an #N/A error. Use explicit input validation or mark unavailable values with =NA() when appropriate.
Entered "#N/A" as text and got the text back Quotation marks produce a text literal, not the PlanMaker error value. Use =NA() in the source cell for the exercise.
Got #NULL! Review spelling, parentheses, argument separators and required arguments. PlanMaker documents #NULL! for invalid formulas and function calls.
Source unexpectedly became zero Determine whether the referenced cell truly contains numeric zero or a blank; do not assume IFNA converts missing data to zero.
Text fallback prevents totals Avoid summing display messages as if they were numeric data; keep a separate numeric source or explicit status column.
Imported workbook behaves differently Recheck cell types, #N/A propagation and file format in the target spreadsheet application.

IFNA versus IFERROR: decision table

Source value IFNA fallback? IFERROR fallback?
42 (valid numeric value) No No
0 (valid zero) No No
#N/A Yes Yes
#DIV/0! No Yes
#REF! No Yes

These comparisons describe error classes from the vendor help and expected logical outcomes. They are not measured PlanMaker run outputs.

Release, platform and Excel compatibility

Environment Documented fact Unverified detail
PlanMaker 2021 2021 English help includes IFNA(Cell, Value) and the #N/A-only description. First release that introduced IFNA; per-edition behavior.
PlanMaker 2024 2024 English help has the same parameters and behavior. Native execution and mobile differences.
PlanMaker 2026 2026 English help has the same parameters and behavior. Native execution and build/platform-specific behavior.
Microsoft Excel before 2013 SoftMaker explicitly says this function is unknown to these Excel releases. Detailed import/conversion behavior for every legacy file format.
Excel 2013 and later SoftMaker identifies 2013 as the start of Excel IFNA support. Exact third-party interoperability of arbitrary nested formulas and locales.

No specific PlanMaker first-support date can be concluded from the documented 2021/2024/2026 manuals. Do not interpret the Excel 2013 compatibility statement as a PlanMaker release date. Documentation is for the PlanMaker desktop family; specific Windows/macOS/Linux and mobile runs, as well as edition restrictions, were not exercised here. IFNA’s help page does not contain the same explicit .xls freeze warning found on IFERROR’s page, so this guide does not automatically attach that claim to IFNA.

Official documentation examined October 11, 2026:

Official reference and verification

Verification status: Official documentation checked; example outcomes were independently reasoned or arithmetically checked where applicable. Not executed in SoftMaker PlanMaker.

  • No genuine SoftMaker PlanMaker screenshots are included; this guide does not use mock application images.