0

I am using a calculated field in a custom-list =TEXT(Created,"yyyy-mmm-dd") to change the date format from the original Created date field. At 99% of the time works correctly, but in about 0.4% it result an "1899.Dec.30.". (After 2500 element there are about 10) If I look on the original Created column, the date is correct, only the calculated one is bad.

  1. How can I prevent this error happening?
  2. How can I refresh the value of these fields to show the correct dates everywhere? (Not an editable field)
  • 1
    You could change the sites regional settings to your local region and get correct dates instead of having the hassle of creating calculated columns. support.office.com/en-us/article/… – Christoffer Mar 20 '18 at 13:51
  • Ohh thanks, that is useful to know. I don't know why did I find this solution instead regional setting change when I searched for this last time : / – Nefri Mar 20 '18 at 13:55
1

How can I refresh the value of these fields to show the correct dates everywhere? (Not an editable field)

As it is a Calculated Column, you can delete and recreate it.

How can I prevent this error happening?

This is probably a timing issue, and probably out of reach for an end-user fix. You could use a workflow instead to populate a normal Single Line of Text column. Workflows always run after the item has been saved.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.