ISERR in WPS Spreadsheet: Non-NA Errors and Selective Error Reports
Detect WPS errors other than #N/A, compare ISERR with ISERROR and ISNA, and preserve unavailable observations while labeling other failures.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: ISERR(value) returns TRUE when the supplied value is an error other than #N/A. It returns FALSE for #N/A and for ordinary non-error values. Therefore, FALSE does not by itself prove that the input is usable: an unavailable #N/A observation also returns FALSE.
Availability and version history
- Introduced: documented by 2019-05-14 in official WPS material; original introduction is not established.
- Availability: The shared Windows Personal IS-function lesson names this function; the dedicated lesson’s edition field is blank.
- Scope: exact current supported builds remain unverified; this evidence does not establish equivalent behavior across every WPS client.
- Checked: October 14, 2026 against complete function-specific documentation. Examples are independently modeled; no native WPS test was performed.
Syntax and the important exception
=ISERR(value)
The argument can be a cell or expression. The WPS lesson describes testing errors other than #N/A and demonstrates combining ISERR with IF. Its shorthand “other values return TRUE” belongs to the error-value discussion; it must not be expanded to say that every ordinary number or text value is an error.
Examples use English function names and comma separators. Outputs below are independent Boolean models of the documented rule, not results captured from a native WPS session.
Example 1: contrast actual errors with ordinary values
Enter these controls in A2:A7, then fill =ISERR(A2) down B2:B7:
| Input in A | Value or type | Expected ISERR |
|---|---|---|
=10/2 |
Number 5 | FALSE |
=1/0 |
Actual #DIV/0! error | TRUE |
=NA() |
Actual #N/A error | FALSE |
="#DIV/0!" |
Text | FALSE |
0 |
Number zero | FALSE |
=FALSE() |
Boolean | FALSE |
Only the actual division error is selected. Text that spells #DIV/0! is not an error object, and the #N/A row is deliberately excluded by ISERR’s definition.
Example 2: preserve #N/A while labeling other errors
In C2 enter and fill down:
=IF(ISERR(A2),"Calculation error",A2)
The intended selected outputs are 5, Calculation error, #N/A, the text #DIV/0!, 0 and FALSE. The #N/A row remains an actual error rather than becoming a label or zero.
This mirrors the documented ISERR/IF selection pattern. It is not a universal claim about lazy evaluation of arbitrary expressions in every client. Using a reference to an existing result also avoids writing the same lengthy calculation in multiple places.
Advanced example: build a three-way error report
For the same six inputs:
=IF(ISNA(A2),"Unavailable",IF(ISERR(A2),"Other error","No detected error"))
Expected labels are No detected error, Other error, Unavailable, No detected error, No detected error and No detected error.
The last label is deliberately limited. A string spelling an error has no actual calculation error, but may still violate the intended input policy. A number might also be outside a permitted range while remaining mathematically valid.
Use ISNA for the excluded #N/A category and ISERROR when both error categories should be detected together.
Advanced check: reconcile the error counts
Convert each error test explicitly into an indicator with IF. Across A2:A7:
=IF(ISERR(A2),1,0)has one selected row.=IF(ISNA(A2),1,0)has one selected row.=IF(ISERROR(A2),1,0)has two selected rows.
For these documented error categories, 1 + 1 = 2. ISERR and ISNA select disjoint groups, so their counts do not overlap. This relationship does not certify a complete classification of every future product-specific error code.
Why selective handling changes a report
Suppose an observed column contains 10, an actual #N/A and an actual #DIV/0!. Replacing only ISERR-selected values with zero leaves 10, #N/A and 0. A direct arithmetic total still has an unresolved #N/A dependency.
Replacing all errors instead would yield 10, 0 and 0, which is a different reporting policy. Neither treatment establishes that the missing or failed observations really equal zero. Keep an error flag or coverage count beside any summarized output.
Limits and troubleshooting
The lesson demonstrates suppressing a #VALUE! result in a particular calculation. Its visual cleanup does not repair the invalid source data. Investigate references, types and input conditions before choosing a fallback.
A formula that cannot be parsed may never produce an evaluated argument for ISERR to inspect. Do not promise that this function catches every entry-time syntax problem. These examples also do not establish every array-entry context or exact handling of newer error categories.
Use IFERROR for a deliberately broad fallback and IFNA for a #N/A-specific replacement. ISERR is the narrower diagnostic test for the complementary error category.
References and verification
- WPS Academy: ISERR, 2019-06-18 (Chinese; edition scope as stated above).
- WPS Academy: shared IS-function syntax and nonconversion rule, May 14, 2019 (Windows Personal).
- Editorial testing standards.
The source establishes the cited product behavior and documented history, not a native-tested current release. Additional linked functions retain their own evidence scopes.