NA Function (Gnumeric)

NA() deliberately produces the spreadsheet error value #N/A. Use it to distinguish not available from a valid numerical zero, an empty cell, or a failed calculation. The Gnumeric manual explicitly names the result and documents no arguments [R1]. For example, a reporting sheet may not yet have a measurement for a particular day; recording =NA() makes that missing observation visible rather than silently inserting 0.

NA is not a text label, and #N/A is not a number. A formula that expects a normal numeric result can encounter that error. When a final report needs friendly wording, explicitly handle the error near the display layer with IFNA, rather than replacing the source value [R1, R2].

=NA()

The above call uses zero arguments. Do not supply a string, cell reference or alternate function name; the manual provides only NA() [R1]. Function names here use Gnumeric’s English documentation. The zero-argument syntax has no argument separator or decimal separator, so those common locale settings do not affect this particular formula. The displayed spelling of error labels may vary with translation; this guide cites the English manual’s #N/A [R1].

Scope checked: Gnumeric 1.12.62 in the 1.12 release series, with the 1.12.62 announcement and release marker checked on the access date below [R3, R4]. Catalogue registration does not itself establish which plugins are enabled in a particular installation; this guide makes no native runtime-testing claim [R2].

Enter the following into separate blank cells. All results are documented or logically expected, not captured Gnumeric results.

Each expected Boolean or type code follows the named function’s official description; none of these examples was evaluated with Gnumeric in this research run. IFNA is separately documented under Gnumeric’s Logic category [R5].

Enter these headings, values and formulas in a new sheet:

Why preserve the original B3 error? Analysts can still distinguish the missing measurement from a real zero; the user-facing column D makes the report readable without losing that distinction. The test is reproducible and contains a deliberate missing value. Expected formulas are inferred from the referenced function definitions, not native observations [R1, R5].

Gnumeric documents ISNA for specifically detecting #N/A, ISERR for other error values, and ISERROR for any error value [R1]. To avoid treating every error as an unavailable observation, classify a cell instead of masking all failures:

=IF(ISNA(B3),"Missing observation",IF(ISERR(B3),"Investigate error","Recorded"))

For B3 containing =NA(), the logically expected result is Missing observation. For a valid number the result is Recorded; for a different error such as division by zero the expected classification is Investigate error. This is a documentation-based composition, with Gnumeric execution still pending [R1, R5]. It is safer for auditing than automatically turning every error into the same placeholder.

• I see #N/A instead of a numeric result. That is the designed output of NA(), not an indication that NA malfunctioned [R1]. Check whether the value intentionally marks unavailable data.
• I typed NA without parentheses. The documented worksheet call is =NA() [R1]. Use that exact signature; name-resolution behavior without parentheses was not tested.
• A downstream calculation now shows an error. Identify which input is intentionally missing. Wrap only the presentation formula with IFNA or test with ISNA when a fallback is appropriate [R1, R5]. Do not replace missing numbers with zero unless your analysis genuinely calls for it.
• ISERR(NA()) is false. That is expected because ISERR explicitly excludes #N/A; use ISERROR to catch it as well [R1].
• What about =NA(1) or extra arguments? The manual documents none. Treat such calls as invalid/unsupported syntax; the precise error display is not native-tested in this batch [R1].
• Can NA reveal why the data is missing? No. The function produces only an error value; use an adjacent status or notes column to distinguish late, refused, and not-applicable observations.

The official Gnumeric manual labels NA Microsoft Excel compatible [R1]. This establishes the documented counterpart, not a guarantee that locale translations, interoperability or every surrounding formula is identical. The example expectations on this page are based on Gnumeric documentation. Check imported/exported workbooks in the target application before depending on their error presentation.

Related guides: ISNA (specific missingness), IFNA (fallback), ISERROR (all errors), ISERR (errors other than #N/A), and TYPE (error-type classification).

The official Gnumeric 1.12.62 source archive was checksum-verified; the Information-function callback confirms the documented error classification without requiring inference from another spreadsheet.

• [R1] Gnumeric Project, Information function manual, headings NA, ISNA, ISERR, ISERROR, TYPE. Accessed 2026-10-12. Claims: NA syntax/output/Excel classification; ISNA, ISERR, ISERROR and TYPE definitions.
• [R2] Gnumeric Project, public function catalogue. Accessed 2026-10-12. Claim: NA registered under Information and classed as complete, with basic project testing. That upstream testing label does not prove this draft’s test cases ran.
• [R3] Gnumeric Project, Gnumeric 1.12.62 announcement. Accessed 2026-10-12. Claim: version 1.12.62 is officially announced; not an NA-specific execution trace.
• [R4] GNOME release downloads, 1.12 directory and LATEST-IS-1.12.62 marker. Accessed 2026-10-12. Claim: release-series version scope at review.
• [R5] Gnumeric Project, Logic function manual, IFNA heading. Accessed 2026-10-12. Claim: IFNA provides #N/A-specific fallback (syntax/behavior requires local application confirmation).

Validation: Official documentation and checksum-verified Gnumeric 1.12.62 source were inspected; displayed logical outcomes were independently reasoned. Native Gnumeric execution, screenshots, locale regression and workbook round-trip tests were not performed.