NUMBERVALUE Function (Calligra Sheets)

• Introduced: First release not established; the name is present in Calligra 2.4.0 source.
• Supported in: Calligra Sheets 26.08.2, with the limitations described here; no retirement established.
• Scope: Desktop Sheets with the Text module. Formulas use English names and semicolon separators.
• Checked: October 14, 2026: selected 25.04.2 engine-library formulas and independent reconstructions; 26.08.2 source only. The test locale was C. No GUI-cell, import or other-locale execution is claimed.

NUMBERVALUE attempts to parse text into a numeric value using the calculation locale. The registered two-to-three-argument contract resembles a separator-controlled conversion function, but the callback does not read its second or third argument. This difference is important when importing numbers from another locale. Official function reference.

=NUMBERVALUE(text;decimal_separator[;group_separator])

text is required. A second decimal_separator argument is also required by registration; group_separator is optional. Those names describe the expected interface, not implemented separator control in the inspected versions. Passing only the text produces #VALUE!, despite the callback using only that text. Brackets mark optional arguments and are not typed. Registration and implementation.

Quotation marks identify text results; error tokens without quotes are actual errors. Numeric results are rounded here to twelve decimal places. The reconstruction column applies independent decimal arithmetic or the inspected character/parser rules, rather than claiming another application test.

If a source field contains 1,234.5 and the calculation locale uses period decimals and comma groups, the tested =NUMBERVALUE("1,234.5";".";",") returns 1234.5. Verify the source convention and destination locale before applying this across a column. For a decimal-comma source such as 1,5, supplying comma as argument two did not repair the mismatch: the test returned #VALUE!. Do not describe this function as locale-independent in that workflow.

Compare =NUMBERVALUE("123.5";",") and =NUMBERVALUE("123.5";"."). Both returned 123.5; the executed equality below confirms that changing the argument does not change parsing for this input. The same value succeeds with the literal separator argument "anything". These cases discriminate an ignored parameter from a genuinely configurable parser.

The underlying locale reader accepts the tested exponent string 1e3 as 1000 and leading/trailing spaces around 12.5. A numeric first argument is converted to text and parsed again. Grouping must match the reader’s accepted structure: the tested 1,5 is not accepted as either a decimal-comma number or a valid three-digit group in the C locale.

=NUMBERVALUE("123.5";",")=NUMBERVALUE("123.5";".")

The executed result was TRUE.

Empty text, nonnumeric text, the mixed-style 1.234,5, and the percentage text 12% produced #VALUE! in the retained tests. Do not generalize these examples into a universal list for every locale. This guide does not claim that changing the workbook’s locale was tested.

No alternate separator-aware Calligra formula is asserted here. Where the import convention differs, normalize and validate the data under an explicit input specification before converting it. In particular, blindly removing punctuation can turn an invalid number into a different valid number. The limitation is an inspected current implementation gap, not evidence that the function has been retired.

• Function-specific implementation
• Versioned implementation reference
• Locale Default
• Locale Constructor
• Number Reader
• String Conversion

The complete selected callback is byte-identical in the inspected 25.04.2 and 26.08.2 sources. The text module has an unrelated SEARCH change; whole-file equality is not claimed. The locale helpers are byte-identical. These comparisons do not establish execution of the later release.

ISNUMBER, SUBSTITUTE.