← All functions

IFNA

Supported, behaves as documented

Category: Logical · Last tested 2026-09-01

Real compatibility results for the IFNA function: executed in Excel for the web, Google Sheets and LibreOffice Calc, with desktop Excel behavior from Microsoft’s official documentation (we do not run desktop Excel — Excel for the web is a different application and is executed separately). Syntax and links to that documentation are below.

Support matrix

EngineDocumentedLive-testedVerdict
Excel (desktop)Yes No — documented only n/a
Excel for the web— Yes (recalc, 2026-09-01) Supported, behaves as documented
Google SheetsYes Yes (Drive import, 2026-08-29) Supported, behaves as documented
LibreOffice CalcYes Yes (25.8.7.3, 2026-08-28) Supported, behaves as documented

LibreOffice version history

We executed the same test cases under each LibreOffice release to show exactly when IFNA’s support changed — not documentation claims, real results.

LibreOffice versionVerdictTested
24.2.0.3 Supported, behaves as documented 2026-08-29
24.8.7.2 Supported, behaves as documented 2026-08-29
25.2.0.3 Supported, behaves as documented 2026-08-29
25.8.7.3 Supported, behaves as documented 2026-08-28
Excel for the web: one case set aside as a round-trip artifact. The readback proves this cell became an unresolved external-workbook reference. The uploaded workbook contains no externalLinks part; the downloaded one contains two, targeting Nope and NotACell — the literal text arguments of the INDIRECT calls. Excel for the web read 'Nope'!B2 as a reference into a workbook named Nope and could not resolve it, which is why the cell holds 0 rather than #REF!, why ISERROR is FALSE and why ISREF is TRUE. Whether the blank comes from the declined “trust externally linked workbooks” prompt or from an unresolvable external evaluating empty in this engine, this run cannot tell — and both are facts about the link, not about the function. The value is published as it came back and no verdict is drawn from it.

Executed test cases

Excel for the web (executed 2026-09-01 via OneDrive recalculation)

These values come from Excel for the web, not from desktop Excel. They are two different implementations of the calculation engine, and this run measured only the web one: the corpus was uploaded to OneDrive as .xlsx, recalculated by Excel for the web on open, and downloaded again for readback. Excel for the web is a rolling service with no pinnable version, so the run is identified by its date. Where a value here disagrees with the Expected column — which is Microsoft’s documentation of the desktop product — we cannot tell you whether the web engine diverges from the desktop one or the documentation is wrong about both, because we do not run desktop Excel.

FormulaDescriptionResultExpectedVerdict
=IFNA(MATCH("z",A1:A3,0),"not found") #N/A from a failed MATCH is caught not found not found Matched
=IFNA(10/0,"na") IFNA only catches #N/A; #DIV/0! must pass through unchanged #DIV/0! #DIV/0!
Provenance

Common compat pitfall: IFNA is NOT a general error trap like IFERROR

Matched
=IFNA(10/2,"na") No error: original value passes through 5 5 Matched
=IFNA(INDIRECT("'Nope'!B2"),"x") IFNA only traps #N/A, so the #REF! from an INDIRECT naming a missing sheet must pass straight through 0 #REF!
Provenance

Documented scope difference, not a quirk: IFNA returns value_if_na for #N/A only, while IFERROR traps every error value. Excel function reference: https://support.microsoft.com/en-us/office/excel-functions-alphabetical-b3944572-255d-4efb-bb96-c6d90033e188

Inconclusive

Google Sheets (executed 2026-08-29 via Drive import)

Google Sheets is a rolling service with no pinnable version, so this run is identified by its date. The corpus was imported to Drive as .xlsx, recalculated by Sheets, and exported back for readback.

FormulaDescriptionResultExpectedVerdict
=IFNA(MATCH("z",A1:A3,0),"not found") #N/A from a failed MATCH is caught not found not found Matched
=IFNA(10/0,"na") IFNA only catches #N/A; #DIV/0! must pass through unchanged #DIV/0! #DIV/0!
Provenance

Common compat pitfall: IFNA is NOT a general error trap like IFERROR

Matched
=IFNA(10/2,"na") No error: original value passes through 5 5 Matched
=IFNA(INDIRECT("'Nope'!B2"),"x") IFNA only traps #N/A, so the #REF! from an INDIRECT naming a missing sheet must pass straight through #REF! #REF!
Provenance

Documented scope difference, not a quirk: IFNA returns value_if_na for #N/A only, while IFERROR traps every error value. Excel function reference: https://support.microsoft.com/en-us/office/excel-functions-alphabetical-b3944572-255d-4efb-bb96-c6d90033e188

Matched

LibreOffice Calc 25.8.7.3 (tested 2026-08-28)

FormulaDescriptionResultExpectedVerdict
=IFNA(MATCH("z",A1:A3,0),"not found") #N/A from a failed MATCH is caught not found not found Matched
=IFNA(10/0,"na") IFNA only catches #N/A; #DIV/0! must pass through unchanged #DIV/0! #DIV/0!
Provenance

Common compat pitfall: IFNA is NOT a general error trap like IFERROR

Matched
=IFNA(10/2,"na") No error: original value passes through 5 5 Matched
=IFNA(INDIRECT("'Nope'!B2"),"x") IFNA only traps #N/A, so the #REF! from an INDIRECT naming a missing sheet must pass straight through #REF! #REF!
Provenance

Documented scope difference, not a quirk: IFNA returns value_if_na for #N/A only, while IFERROR traps every error value. Excel function reference: https://support.microsoft.com/en-us/office/excel-functions-alphabetical-b3944572-255d-4efb-bb96-c6d90033e188

Matched

Docs & syntax

Where IFNA behaves differently

Compared against other functions