Contact

PlanMaker DATEVALUE Function: Convert Date Text into a Serial Date

Date and Time Beginner SoftMaker PlanMaker 2026

Convert text dates to serial numbers with DATEVALUE in SoftMaker PlanMaker 2026. Includes locale-safe input advice, worksheet examples, errors and Excel 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: =DATEVALUE("09/25/2018") returns the serial number 43368 according to SoftMaker’s PlanMaker 2026 DATEVALUE reference. The number can then be displayed as 09/25/2018 by applying a date format. DATEVALUE does not just change how characters look: it requests conversion of a recognized text date to a numeric date value.

Verification: Official PlanMaker 2021, 2024, and 2026 reference pages checked 2026-10-11 UTC, with independent date arithmetic for selected examples. No native PlanMaker, Excel, or mobile execution was available. Results beyond the vendor’s explicit example are labeled expected if the local date parser recognizes the input. Screenshots are not presented as application evidence.

When this function helps

Use DATEVALUE when a date arrives as text, such as a date column exported from a stock system, an archived CSV or a downloaded order report. Once interpreted as a serial value, dates can be sorted chronologically, used in subtracting elapsed days and displayed using a selected date format. An imported string that looks like a date is not proof that the sheet stored it as a date number.

PlanMaker calls DATEVALUE a compatibility function: modern PlanMaker often converts date-like text when a calculation needs a date. Explicit DATEVALUE can still make the intent visible and simplify review of imported text. Do not convert arbitrary identifiers that merely resemble dates; preserve original values in a separate source column. Vendor description.

Official syntax and argument order

=DATEVALUE(Text)
Argument Required? Type What it means Default
Text Yes Text string representing a date, or a cell reference to such text Value that PlanMaker will attempt to interpret as a date None

There is one required argument; do not put a second date-format argument inside this function. Wrap literal text in double quotes, such as "09/25/2018"; reference a cell without quotes, such as A2. The exact spelling and argument order are from the official 2026 page. With one argument, formula-list separators are not an issue inside DATEVALUE, but locales can change which date strings can be parsed. The English examples use month/day/year, not a universal day/month/year promise. PlanMaker’s data-entry notes.

Reproduce a small import worksheet

Before entering A2:A4, set column A to Text (or import these strings as text), so PlanMaker does not automatically convert them before DATEVALUE runs. Use an installation configured to recognize the official U.S.-style MM/DD/YYYY date strings.

Row A: Imported text Formula in B Expected numeric B Basis
2 09/25/2018 =DATEVALUE(A2) 43368 Explicit SoftMaker 2026 worked example
3 09/26/2018 =DATEVALUE(A3) 43369 Independent next-day serial arithmetic; needs native parser confirmation
4 09/30/2018 =DATEVALUE(A4) 43373 Independent five-day difference; needs native parser confirmation

Enter the formulas separately in B2:B4 and set B2:B4 to a number display if the application initially shows formatted dates. When you apply the date format M/D/YYYY, the numeric result 43368 is displayed as 9/25/2018; the underlying result remains numeric. This is the documented distinction between a date serial and its presentation. DATEVALUE · number formatting.

To check that the converted values are useful for calculations, enter in C3:

=B3-B2

Expected: 1 day. In C4 enter =B4-B2; expected: 5 days. These are independently calculated differences conditional on the dates being parsed correctly, not observed native PlanMaker outputs. Keep the output cells formatted as numbers to see day counts.

Entering a date from its components is often safer

If the source stores year, month and day in separate numeric fields, avoid guessing its region-specific text order:

=DATE(2018,9,25)

SoftMaker documents this expression returning 43368. This is a different function: DATE takes Year, Month, Day numeric components; DATEVALUE takes one date-containing text argument. Official DATE.

Advanced case: validate an imported delivery timeline

Suppose your order system exports the text dates shown in A2:A4, and you need elapsed calendar days from the first delivery. Keep the original string column visible for audit. Convert with =DATEVALUE(A2) in B2, fill downward, and calculate =B3-$B$2 in C3 and =B4-$B$2 in C4. A dollar sign locks the base date row during copying. Expected elapsed days are 1 and 5. This is calendar day arithmetic, not business-day counting; it makes no promises about time zones, holiday calendars or partial days.

For ambiguous imported text such as 03/04/2026, two regional interpretations are possible. Do not silently claim the date is March 4: verify source specifications first. If the import contains full day/month/year components, consider building the date from numeric parts with DATE; if the source already contains true date serials, reformat the cell rather than converting text. Regional data-entry guidance.

Troubleshooting: why a date may not convert

Symptom Check and correction
A date appears as 43368 This is expected for a numeric serial. Choose a date cell format, not a different formula.
An imported date is not recognized Inspect the imported text type, character order, separators and local region. Reimport the source as text and compare one known row to a date created with DATE.
03/04/2026 converts to an unexpected date Its month/day order is ambiguous across locales. Require an unambiguous source mapping, and verify an individual record before converting the whole column.
An error appears for text that is not a date The general PlanMaker error-value reference describes #VALUE! for inappropriate value types. The DATEVALUE-specific result for every invalid string was not native-tested; note the actual displayed code rather than assuming.
Formula shows #NULL! PlanMaker documents this for malformed formulas, missing/extra arguments and nonstandard pasted quotation marks; use plain double quotes and the one-argument syntax.
Numbers unexpectedly vary after Excel export Compare the resulting displayed dates, not just raw serials. Date-system settings and locale differences have not been tested in this research.

PlanMaker’s data-entry chapter says dates range from January 1, 1900 through December 31, 2500 for manually entered dates, and interprets two-digit years 00–29 as 2000–2029 and 30–99 as 1930–1999. That is general data-entry documentation, not a native test establishing every DATEVALUE edge case. Use four-digit years and avoid using an unspecified DATEVALUE domain beyond these documented examples. Vendor data entry.

Versions, platforms and Excel compatibility

The official PlanMaker 2021, 2024, and 2026/NX English help pages all document the one-argument DATEVALUE(Text) function and the "09/25/2018" → 43368 example. This demonstrates documented availability in those versions; it does not prove support in every edition, local language, Android or iOS interface, nor that behavior is identical under every regional setting. The 2026 help separately lists Windows, macOS, Linux, Android and iOS system requirements; this is not a per-function test. 2021 · 2024 · 2026 · platform requirements.

Microsoft Excel DATEVALUE likewise converts date text to a serial number, and Microsoft explicitly notes regional-system settings and a 1900-based default date system for Excel. Similar spelling and one-argument syntax are not proof that all inputs, error values, 1900-boundary dates or alternative date systems survive conversion unchanged. In a mixed Excel/PlanMaker workflow, test dates after export and reopen the file, especially when users have different date locales. Do not assume Excel’s documented year-omission or time-portion rules apply to PlanMaker without its own evidence.

Browse the PlanMaker function directory · Compare spreadsheet functions.

Verification: Official vendor references and Microsoft compatibility documentation accessed 2026-10-11 UTC. Official sample 43368 is documented; subsequent date differences were independently calculated. Native PlanMaker execution was not performed.