N in SoftMaker PlanMaker: Convert Values to Numeric Results
Use N to distinguish actual numbers from numbers stored as text, with test data, boolean cases, dates and migration notes.
Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in SoftMaker PlanMaker 2026. How formula examples are checked
Quick answer: =N("42") is expected to return 0, not 42. The value inside quotation marks is text. In contrast, =N(42) returns 42, and =N(TRUE) returns 1. PlanMaker documents N chiefly as an older-spreadsheet compatibility function. Official PlanMaker 2026 N documentation.
Why and when to use N
N checks an expression and produces its numeric representation when the input is an actual number, date serial, or logical TRUE/FALSE; the vendor specifies zero for other values. The distinction is useful when inspecting imported worksheets or an inherited formula that uses N for compatibility. Do not use N to parse a numeric-looking text string. VALUE and NUMBERVALUE solve different conversion tasks.
Verified syntax and argument contract
=N(Value)
| Argument | Required | Type and meaning | Default |
|---|---|---|---|
Value |
Yes | Numeric value, actual date value, Boolean, cell reference, or expression | None |
Only one argument is documented; there is no optional mode or parsing separator. Square brackets do not occur in the syntax. The official English references use this signature in PlanMaker 2021, 2024 and 2026. The documented cases include numerics unchanged, TRUE → 1, genuine date values → date serials, and nonnumeric text → 0. FALSE → 0 is the expected numeric logical mapping; verify it in the target build. These statements concern documented inputs: error propagation from an error-valued argument has not been executed in PlanMaker and is not asserted here. Sources: 2026 N; 2024 N; 2021 N.
Reproducible practice worksheet
Start a new, empty spreadsheet. In column A type the following expressions, including the leading = for the rows shown. Each cell should contain the result/type described, not literal quotation marks unless shown in a formula.
| Row | Enter in column A | Underlying result type | Enter in column B | Expected B |
|---|---|---|---|---|
| 2 | =7.5 |
Number 7.5 | =N(A2) |
7.5 |
| 3 | ="7.5" |
Text “7.5” | =N(A3) |
0 |
| 4 | =TRUE |
Logical TRUE | =N(A4) |
1 |
| 5 | =FALSE |
Logical FALSE | =N(A5) |
0 |
| 6 | ="Pending" |
Text “Pending” | =N(A6) |
0 |
The B-column outputs follow SoftMaker’s conversion rules and the expected FALSE-to-zero numeric mapping. Validation: documentation checking plus independent type-based calculation; these are expected results, not observed PlanMaker outputs. You can also type =N("42") and =N(42) into blank cells and compare the expected results 0 and 42.
Advanced example 1: make a numeric quality-control flag
If C2 contains actual Boolean TRUE, =N(C2) is expected 1; if C3 contains FALSE, =N(C3) is expected 0. In an inherited workbook this can convert a Boolean flag to a 1/0 marker. But the same operation would also map an arbitrary text status to 0, hiding the difference between FALSE and invalid text. Do not interpret 0 as a validated failure decision unless the input type was checked.
Advanced example 2: dates and serial-number gotchas
For a real date value representing September 25, 2014 in A1, the vendor’s example gives =N(A1) → 41907. This is a numeric date serial, not the formatted date string. A text literal ="09/25/2014" is still text and belongs in the category that N converts to zero. Date entry interpretation and display depend on locale. Do not infer that other workbook date systems, imported files or mobile editions were tested. SoftMaker documented date example.
Errors, limits and troubleshooting
- N unexpectedly returns 0 for “42”: this is documented behavior, not a rounding error. Use
=VALUE("42")for a numeric text string. - An apparent date returns 0: verify that the cell stores a real date serial rather than a text string; the appearance of a formatted date alone cannot prove its stored type.
- Zero is ambiguous: N may return 0 for genuine numeric zero, FALSE, or nonnumeric text. Inspect the input before using N as a data-quality gate.
- Formula appears as text: formulas must start with
=; the vendor explains this in Formula basics. - Unexpected error codes: no malformed-input or error-valued-argument results have been executed natively. Inspect upstream formulas and preserve the original error instead of assuming a specific behavior.
- Locale: this one-argument formula has no separator, but date recognition, decimal entry and Boolean display can vary with locale and source-file conventions. The reproducible 7.5 examples assume a decimal-point locale.
Editions, compatibility and other functions
The N function is documented in the 2021, 2024, and 2026/NX English manuals; that does not establish its first introduction, every licence tier, mobile feature parity or identical execution on Windows/macOS/Linux/Android/iOS. Microsoft’s Excel N documentation describes a closely related numeric/Boolean/date mapping. Excel explicitly discusses error input; do not transplant that as a native PlanMaker observation. For numeric strings use the official VALUE; for explicit decimal and thousands separators use NUMBERVALUE.
Evidence and validation log
- SoftMaker N, PlanMaker 2026 — one-argument syntax; numeric, text, Boolean and dated example; compatibility purpose. Accessed 2026-10-11 UTC.
- SoftMaker N, PlanMaker 2024 — documented matching syntax/behavior. Accessed 2026-10-11 UTC.
- SoftMaker N, PlanMaker 2021 — documented matching syntax/behavior. Accessed 2026-10-11 UTC.
- Microsoft Excel N function — comparison only. Accessed 2026-10-11 UTC.
Verification: Official documentation checked; independent type/Boolean examples calculated. Native PlanMaker execution: 0. Cross-app execution: 0. Observed PlanMaker results: none.