N in Collabora Office: Numeric Conversion Without Parsing Text

• Introduced: original Collabora release and launch date are not established by the sources reviewed.
• Availability: documented in Collabora Office 26.04 help, scoped to the desktop-help release.
• Platform scope: support in every online or mobile deployment is not inferred from desktop documentation.
• Checked: October 14, 2026. Complete function-specific documentation and independent controls; no native Collabora test was performed.

=N(123)
=N(TRUE())
=N(FALSE())
=N("123")

Expected results are 123, 1, 0 and 0. The last control does not parse the characters into the number 123. If the objective is numeric text parsing, use a deliberately chosen conversion with its own locale and input rules.

Examples use English function names and semicolon separators in multiargument helper formulas. They are independently modeled expectations, not native Collabora execution records.

Enter the following values or formulas in A2:A8. Fill =N(A2) down B2:B8.

The converted values total 16.5. This total follows N’s policy; it does not establish that every original observation was a valid quantity. Numeric-looking text 20 contributes zero, while the Boolean TRUE contributes one.

Use ISNUMBER on the original values if the question is whether they are already numbers. N and a type test answer different questions.

Enter numeric quantities 0, 4, 7 and 10 in D2:D5. Fill this formula down E2:E5:

=N(D2>=5)

Expected indicators are 0, 0, 1 and 1, totaling 2. Each comparison first produces a Boolean, and N applies its documented Boolean conversion.

For these four valid observations, the proportion meeting the threshold is 2/4 = 0.5. The denominator is explicit. This example does not decide what to do with missing, erroneous or numeric-looking text quantities.

The alternative =IF(D2>=5;1;0) produces the same indicators for the stated numeric fixture. Neither construction validates the business meaning of the original inputs.

Against the original A2:A8 type table, evaluate:

=IF(ISNUMBER(A2);A2;0)

Filled down, expected outputs are 20, -4.5, 0, 0, 0, 0 and 0, totaling 15.5. This differs from N’s 16.5 because the explicit numeric-type policy does not count the Boolean TRUE as an original numeric observation.

Both policies still give zero for text 20. If that string was intended to represent a quantity, neither has parsed it. Confirm its meaning and locale before considering VALUE; do not convert identifiers simply to make them pass a numeric test.

=N(1/0)
=N(NA())
=N("#N/A")

Expected results are #DIV/0!, #N/A and 0. The first two inputs are actual errors; the third is a text label. The source explicitly demonstrates N(1/0) preserving the division error.

If a surrounding IFERROR changes that error into zero, the change belongs to the fallback policy, not N. Keep an error flag if the distinction between failed and measured-zero observations matters.

=ISNUMBER("20")
=ISNUMBER(N("20"))

Expected results are FALSE and TRUE. The second test sees the converted numeric zero, not the original string. It cannot prove that the text was successfully parsed into twenty.

Likewise, =100+N("Reviewed") has expected result 100 because the text contributes zero. Such embedded text is not proof that a review took place and is not a substitute for an actual approval record.

The current help establishes the scalar number, Boolean, text and error rules above. This guide does not certify every empty-reference, array, historical date-serial or imported-object case.

Choose ISNUMBER for a type predicate, VALUE for deliberately parsed text and N for its particular conversion policy. Preserving the original inputs makes the difference visible when a report’s total changes.

• Collabora Office 26.04: N.
• Editorial testing standards.

The complete function section was reviewed. Worked controls are independently checked expectations; native execution, broader client support and unlisted edge cases remain unverified.