Browse

IFERROR in SoftMaker PlanMaker: Replace Formula Errors Safely

Logical Intermediate SoftMaker PlanMaker 2026

Learn PlanMaker IFERROR with verified syntax, division-by-zero examples, error-handling strategies, file-format caveats and release 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

IFERROR in SoftMaker PlanMaker: show a useful result instead of a formula error

Quick answer: =IFERROR(B3/C3,"Check order quantity") returns expected Check order quantity when B3 contains 6 and C3 contains 0. Without the wrapper, the division returns #DIV/0!. When there is no error, IFERROR returns the calculation’s ordinary result. This behavior is explicitly described in SoftMaker’s PlanMaker 2026 IFERROR documentation.

Use IFERROR for reporting values that must remain readable despite a calculation error. Do not use it to conceal mistakes in source data: a fallback message should make it obvious that a result requires attention.

Official syntax, parameters and return value

The vendor’s English-language function entry gives the exact syntax below (the leading = is needed when entering the function as a cell formula):

=IFERROR(Value, ValueIfError)
Argument Type / purpose Required Default
Value A value or calculation to return normally, such as B3/C3, or a reference like D3. Yes None.
ValueIfError The alternative value when Value evaluates to an error. For example, "Check order quantity", 0, or an empty text string "". Yes None.

Return behavior: When Value is valid, return that result unchanged; if it evaluates to any type of PlanMaker error, return ValueIfError instead. IFERROR does not distinguish #DIV/0! from #N/A or #REF!. For an #N/A-only fallback use the separately documented IFNA function; it has a narrower purpose.

In the examples, use commas as in the official English function syntax. Formula entry starts with =. Country settings can affect numeric separators; the function dialog (Formula → Function) shows how your installation expects its arguments. No locale-specific delimiter was tested in a running copy of PlanMaker. The syntax above is a documentation transcription, not the output of a native test.

Copyable practice sheet: delivery completion rate

Open a blank sheet and enter these exact numbers (not number-shaped text). All five rows are deliberately simple so the answer can be checked independently.

Row A: Item B: Delivered C: Ordered
2 Pens 8 10
3 Paper 6 0
4 Tape 12 12
5 Clips 3 5
6 Folders 0 4

Put the formulas in column E; do not enter formulas over the source data.

Example 1: keep valid calculations intact

  1. Enter the table above, then select E2.
  2. Type =IFERROR(B2/C2,"Check order quantity") and confirm the formula.
  3. Expected E2: 0.8 because 8 ÷ 10 = 0.8, a valid numeric result. It is not replaced by the error message.
  4. Format the result cell as Percentage if desired; it will then display 80% without altering the numeric result 0.8.

Example 2: handle zero in the denominator

  1. Select E3 and enter the formula with the next row’s references:

    =IFERROR(B3/C3,"Check order quantity")

  2. B3/C3 means 6 ÷ 0, so the unwrapped expression is expected to produce #DIV/0! (see SoftMaker error values).

  3. Expected E3: Check order quantity because the second IFERROR argument is selected when the first produces an error.

  4. Correct the underlying source value in C3 before using the rate in a report; a fallback does not repair the data.

Example 3: fill down and inspect each answer

Enter =IFERROR(B2/C2,"Check order quantity") in E2 and copy it through E6. Cell references are relative, so they advance with the row.

Destination Inner expression Expected IFERROR result Independent check
E2 8 / 10 0.8 ordinary numeric result
E3 6 / 0 Check order quantity division-by-zero error intercepted
E4 12 / 12 1 full completion
E5 3 / 5 0.6 partial completion
E6 0 / 4 0 valid zero, not an error

Notice the distinction between a mathematically valid zero and a calculation error. Replacing all zeros with a fallback would require a different condition, not IFERROR alone.

Advanced application: distinguish invalid source data from other errors

For a dashboard, it is often more useful to flag a known invalid denominator explicitly. In F3, enter:

=IF(C3=0,"Invalid ordered quantity",IFERROR(B3/C3,"Review calculation"))

Expected F3: Invalid ordered quantity. The existing IF function detects the zero denominator before the nested calculation is needed. For row 4, the same formula with 3 changed to 4 has expected result 1. This makes a known input problem different from an otherwise unexpected calculation failure.

If a result is to be summed later, consider an explicit numeric policy. =IFERROR(B3/C3,0) has an expected value 0 for row 3, but silently treating invalid data as zero can distort averages and totals. Use zero only when it has a defensible meaning for your workflow.

Common mistakes and troubleshooting

Symptom Likely reason Check or correction
#DIV/0! still appears IFERROR wrapper was not applied to the calculation that actually fails, or the formula refers to a different cell. Inspect the formula bar and compare references; use =IFERROR(B3/C3,"Check order quantity").
#NULL! Mistyped function, missing bracket, wrong argument count or problematic copied quotation marks. Re-enter plain straight quotation marks and both required arguments; check the application’s function dialog. See the vendor’s error-value reference.
Every result shows the fallback The underlying source calculation fails in every row, or the wrong ranges were copied. Temporarily examine the original calculation separately and trace the source values.
A report shows 0 where data is missing Using 0 as a blanket fallback conceals the error. Prefer a diagnostic text message or use a separate validation status.
An #N/A lookup should be handled but other errors must remain visible IFERROR catches all error types. Use IFNA for that narrower policy.
A valid result displays unexpectedly as 80% or 0.8 Cell formatting differs. Check the cell’s number format; the underlying value is still 0.8.

Limits worth knowing

  • IFERROR is not a data-quality test. A valid but wrong numeric value passes through unchanged.
  • Different errors collapse into one fallback. That makes a dashboard tidy but can make diagnosis harder.
  • Supplying both arguments is mandatory in the documented syntax. The manual does not give argument defaults.
  • The vendor does not document a special numerical tolerance or any release-specific evaluation-order rule on this individual help page; this guide does not invent one.

Version, platform and file-format compatibility

Environment Confirmed from official material Not established
PlanMaker 2021 The 2021 English manual documents IFERROR(Value, ValueIfError) and describes a fallback on any error. Exact first-ever supported release, edition differences, actual application execution.
PlanMaker 2024 The 2024 English manual gives matching syntax and behavior. Exact desktop build and mobile behavior.
PlanMaker 2026 The 2026 English manual gives matching syntax and behavior. Native results, platform-specific differences.
Legacy Excel .xls (Excel 2003 and earlier) SoftMaker explicitly warns IFERROR is not representable in that format: saving converts such calculations to fixed results. Whether a different conversion path preserves a formula; do not depend on it.
PlanMaker .pmdx / modern .xlsx SoftMaker recommends these rather than legacy .xls for this function. Complete interchange equivalence for all workbooks or third-party editors.

The 2021, 2024 and 2026 manuals are evidence that IFERROR is documented in those releases, not that it first appeared in 2021. This batch did not examine a native copy of PlanMaker on Windows, macOS, Linux, Android or iOS. The 2026 documentation is presented for the PlanMaker 2026/NX family; edition-specific tests are outstanding.

Cross-software caution: Excel also uses the familiar IFERROR(value,value_if_error) style, but don’t assume an imported workbook preserves error types, delimiters, formulas or results in every format. In particular, SoftMaker’s .xls fixed-result warning is more important for migration planning than the similarity of the formula name.

The authoritative vendor pages were inspected on 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.