ISNA Function in ONLYOFFICE Spreadsheet Editor: Formula, Examples, Errors
Distinguish unavailable lookup results from division and reference errors using ISNA, with reproducible examples.
Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in ONLYOFFICE Spreadsheet Editor. How formula examples are checked
Quick answer
Use =ISNA(value) to ask whether a value or cell specifically evaluates to the #N/A error. A TRUE result means #N/A; a FALSE result means the value is not #N/A—including when it is another type of error. This narrow distinction is documented in the ONLYOFFICE ISNA reference. The examples below are expected classifications and were not executed in ONLYOFFICE.
Purpose and exact syntax
=ISNA(value)
| Argument | Required? | Allowed concept / types | Default |
|---|---|---|---|
value |
Yes | An expression, single-cell reference, number, text, logical value, error, empty cell, or name referring to one of these. | None documented. |
ONLYOFFICE categorizes ISNA as an Information function. It returns a Boolean TRUE only for the #N/A error token, and FALSE for other values. The function does not find missing records by itself; it only tests the result of a lookup or another expression. ISNA, ISERROR and IFNA are three distinct functions, not spelling aliases.
Copyable worksheet: distinguish unavailable from broken
In a blank worksheet enter these specific formulas/values in A2:A7. In B2 enter =ISNA(A2) and fill through B7. Use an actually blank A7 cell (clear its contents).
| Row | A: Enter or leave | Expected A value | Expected B | Reason |
|---|---|---|---|---|
| 2 | =NA() |
#N/A |
TRUE |
Real unavailable-value error. |
| 3 | =1/0 |
#DIV/0! |
FALSE |
Error, but not #N/A. |
| 4 | ="#N/A" |
Text #N/A |
FALSE |
Quoted string, not an error value. |
| 5 | =12 |
Number 12 | FALSE |
Numeric value. |
| 6 | =SUM(2,3) |
Number 5 | FALSE |
Successful calculation. |
| 7 | leave empty | Genuine blank | FALSE |
Blank is not #N/A. |
For a direct test that needs no references, use:
=ISNA(NA())
Expected: TRUE. Compare:
=ISNA(1/0)
Expected: FALSE. These are checks against the specific error category, not a claim that errors are harmless. =NA() is officially documented to create a #N/A value. The source and distinction are documented in the NA function reference, ISNA reference, and ISERROR reference.
Independent validation: simple arithmetic and vendor-described error categories were checked independently; no installed editor, screenshots or native workbook results are available.
Advanced: a useful lookup audit pattern
Consider a result column C with values fetched from an external product-code lookup. For each row, keep the raw lookup result in C2. In D2:
=IF(ISNA(C2),"Code not found",C2)
When C2 is a genuine #N/A, the expected D2 text is Code not found. When C2 is 25, D2 should be 25. When C2 contains #DIV/0!, ISNA is expected to be FALSE: D2 may still expose an error, which is preferable to falsely labeling an invalid calculation as a missing product. Test this last scenario in the target editor because expression evaluation, lazy branches and error propagation need native confirmation.
For a small, fully specified lookup table, populate F2:G4:
| Row | F: Code | G: Stock |
|---|---|---|
| 2 | A-10 | 8 |
| 3 | B-20 | 5 |
| 4 | C-30 | 0 |
With all code cells entered as text, the following is a cross-function expected example:
=ISNA(VLOOKUP("Z-99",F2:G4,2,FALSE))
Expected: TRUE if the installed ONLYOFFICE build’s exact-match VLOOKUP follows the official VLOOKUP documentation, because Z-99 is absent. The expression is not natively executed here; this is not proof of the editor’s output on your installed version.
Compare detection with replacement
| Function | Example | Expected result | Distinction |
|---|---|---|---|
ISNA |
=ISNA(NA()) |
TRUE | Narrow TRUE/FALSE test for #N/A. |
ISERROR |
=ISERROR(1/0) |
TRUE | Broad test including #DIV/0!. |
IFNA |
=IFNA(NA(),"Missing") |
Missing |
Returns a fallback rather than a Boolean test. |
IFERROR |
=IFERROR(1/0,"Review") |
Review |
Replaces a broader set of errors. |
IFNA uses value, value_if_na with exactly that argument order according to its official help. Do not use a broad IFERROR fallback when you need non-#N/A errors to remain visible for debugging.
Interpreting blanks and errors
- The string
"#N/A"imported from a file and the actual formula error#N/Aare not equivalent. If text entered as a label is mistaken for an error, ISNA should return FALSE. #REF!indicates a reference issue;#DIV/0!indicates a denominator issue. They should not be relabeled “not available” solely because a user sees an error on screen.- An empty cell is not the same as
=NA(). Explicitly document when your business process uses a blank to mean “unknown” versus the genuine #N/A error used by this function. - ISNA’s official article does not enumerate every possible interaction with array results, text coercion, 3D references or all localized versions; test such scenarios natively before offering guarantees.
Versions, platforms, and locale — what has actually been verified
This guide reflects the English, unversioned ONLYOFFICE documentation accessed 2026-10-13 (UTC). The function is listed in the official Spreadsheet Editor function catalogue. The catalogue is a published function list, not a platform/version certification matrix:
- ONLYOFFICE Docs / online Spreadsheet Editor: listed in current vendor help, but not executed in a browser-based installation for this guide. Docs 10.0 was announced on October 10, 2026; that announcement does not prove these results for every earlier Docs build.
- ONLYOFFICE Desktop Editors: the desktop changelog has a 9.4.0 entry dated May 19, 2026, but it does not identify the first implementation of this particular function. No Windows, macOS, or Linux Desktop build was executed. Do not treat documentation presence as proof of feature parity.
- Mobile/integrations: not tested. The page does not claim all connectors or mobile editions have identical calculation behaviour.
- Language and separators: the Advanced Settings guide documents Formula Language, regional formats, and separator controls. The function-entry guide shows English function names and commas for multi-argument calls. Each top-level function here has one required argument, so it has no internal list separator, but surrounding
IForIFERRORformulas use English comma-separated syntax. Localized formula names, input delimiters, data-import types, or output display can vary. Adjust formulas to the actual editor settings instead of blindly swapping punctuation.
Validation declaration: examples are documented or independently reasoned expected outputs, not results observed from ONLYOFFICE. For the comparison-function cases, only formula specifications—not a live workbook—were checked.
Test and troubleshooting protocol
- Open a new test workbook and enter the exact formulas above into the specified cells (not an existing production workbook).
- Verify that formula cells begin with
=. A cell containing the literal text"#N/A"is not the error generated by=NA(); a number stored as text may look numeric but is a different type. - Reproduce the simple direct-expression test first, then the reference-cell test. Compare cell types, not just displayed formatting; distinguish an actual spreadsheet error from text that spells an error name.
- Confirm English formula language and your argument separators in advanced settings. If your version reports an unknown function, confirm application version and support from the vendor—do not rename a function based on a guessed alias.
- If a sample differs from the table, preserve the workbook and record editor product (Docs web/server or Desktop), exact build, operating system, locale, formula, and resulting observed cell value. Such observations are necessary before asserting platform-specific behaviour.
Common pitfalls
- A leading apostrophe or preformatted Text cell can store
=IS...as literal text instead of calculating it. Change the cell type, re-enter the expression, and test again. - A quoted error string such as
"#N/A"is not an error result. Generate a genuine error with=NA()or=1/0in the fixtures. - A blank cell, zero, and the empty string (
"") differ. This is especially relevant when validating imported CSV data or formulas returning empty-looking outputs; do not infer type from cell appearance. - Error tests and error handling are different operations. An
IS*function answers TRUE/FALSE;IFNAorIFERRORsubstitutes a fallback. Use substitution only after deciding whether an error is expected or should be investigated. - Do not hide an unexpected error during auditing. A source input with a genuine
#REF!may mean the workbook structure is broken. A user-facing fallback can mask this issue unless you keep an audit column.
Cross-application interpretation
These functions have counterparts in Microsoft Excel and other spreadsheet applications, but identical spellings do not guarantee identical error propagation, coercion, locale, or array behaviour in every version. The examples are documented for ONLYOFFICE’s English current help, not a tested cross-application equivalence guarantee. For a migrated workbook, verify sample outcomes natively in both source and destination applications.
Native ONLYOFFICE execution and cross-version import behavior remain untested. Preserve source formulas and verify the cases that matter to your workbook in the installed editor.
Official sources and checking dates
- ONLYOFFICE ISNA function reference — official purpose, required argument, syntax, classification, and documented return rule. Accessed 2026-10-13 UTC; unversioned English documentation.
- ONLYOFFICE Spreadsheet Editor — Inserting functions — formula insertion, function list and comma-separated English examples. Accessed 2026-10-13 UTC.
- ONLYOFFICE Spreadsheet Editor — Advanced Settings — formula language, regions and separators. Accessed 2026-10-13 UTC.
- ONLYOFFICE Desktop Editors changelog — Desktop release-history context, not feature-by-build certification. Accessed 2026-10-13 UTC.
- ONLYOFFICE Docs 10.0 announcement, October 10, 2026 — product-version context, not native test evidence. Accessed 2026-10-13 UTC.
Verification: Official syntax and all example classifications were independently checked. No native application or localized execution was performed.