Fix WPS Spreadsheets #VALUE Errors Caused by Regional Date Functions
Question details
The user needs to resolve #VALUE errors in a spreadsheet when DATEVALUE or TIMEVALUE formulas are opened with regional settings that differ from the source data.
- Product
- WPS Spreadsheets
- Device & OS
- not provided
- Scenario
- A workbook containing date and time text functions is opened in WPS Spreadsheets or Excel Online with regional date/time settings that do not match the source data.
- Observed behavior
- Cells display #VALUE errors. Deleting a cell, row, or column can trigger recalculation and temporarily remove the error, but the underlying regional date/time function mismatch remains.
Open the affected workbook in WPS Spreadsheets and select a cell that shows #VALUE. Check the formula bar for DATEVALUE or TIMEVALUE, and note the date/time format used by the source data.
Replace DATEVALUE and TIMEVALUE Functions with Consistent Date or Time Values
Use this solution when a workbook opened with different regional settings returns #VALUE errors from localized date and time text functions.
DATEVALUE and TIMEVALUE convert text into dates and times according to the current regional settings. If the workbook source text uses a different date order or separator, WPS Spreadsheets and Excel Online may fail to parse it and return #VALUE.
Click the cell that displays #VALUE, then look at the formula bar in WPS Spreadsheets to confirm that it uses DATEVALUE or TIMEVALUE.
Press F2 or double-click the cell, remove the DATEVALUE or TIMEVALUE wrapper, and enter the date or time directly in a consistent format such as 2025-01-31 or 14:30.
Select the source cells, go to Home > Number Format, and choose Short Date or Time so all date and time values use the same format.
Press F9 or go to Formulas > Calculate Now to refresh all formulas and verify that #VALUE no longer appears.

Use Evaluate Formula to Locate the Failing Regional Date Reference
Use this solution if you need to identify which part of a longer formula is causing the #VALUE error before editing it.
Fix Regional Date #VALUE Errors in WPS Spreadsheets
Open the affected Excel workbook in WPS Spreadsheets, locate the DATEVALUE or TIMEVALUE formulas, and replace them with consistent date/time values. WPS Spreadsheets supports Excel formula compatibility, so you can correct the regional mismatch directly without switching applications.
- 1. Open the workbook in WPS Spreadsheets: Launch WPS Office, click Menu > Open, and select the Excel workbook that shows #VALUE errors.
- 2. Select the #VALUE error cell: Click the affected cell and inspect the formula bar to identify DATEVALUE or TIMEVALUE.
- 3. Replace the regional date/time function: Press F2, remove the DATEVALUE or TIMEVALUE wrapper, and enter a consistent date/time value or reference.
- 4. Apply a consistent date format: Go to Home > Number Format and choose Short Date or Time for all cells used by the formula.
- 5. Recalculate and save: Press F9 or use Formulas > Calculate Now, then save the workbook as .xlsx to keep the fix.

Frequently Asked Questions
Why do DATEVALUE and TIMEVALUE return #VALUE when I open my file in WPS Spreadsheets?
These functions parse text according to the current regional date and time settings. If the source data uses a different date order or separator, the text cannot be converted and WPS Spreadsheets returns #VALUE.
Is deleting a row or column a permanent fix for the #VALUE error?
No. Deleting a cell, row, or column triggers recalculation and may temporarily hide the error, but the underlying DATEVALUE or TIMEVALUE mismatch remains until you correct the formula or source data.
Can I keep DATEVALUE if I change the regional settings on my computer?
Changing regional settings may help for one workbook, but shared files can still fail on another device. A more reliable fix is to replace the text-parsing function with a consistently formatted date/time value.
Does WPS Spreadsheets support Excel DATEVALUE and TIMEVALUE functions?
Yes. WPS Spreadsheets supports these Excel functions. The #VALUE error is caused by a regional format mismatch, not by missing function support.




