# Date format not recognised

**URL:** <https://connect.superhuman.com/t/date-format-not-recognised/23411>\
**Category:** Ask the Community\
**Created:** [May 13, 2021, 4:38pm UTC](https://connect.superhuman.com/t/date-format-not-recognised/23411 "2021-05-13T16:38:25Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stephen\_Gormley](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/stephen_gormley/32/20903_2.png) [@Stephen\_Gormley](https://connect.superhuman.com/u/Stephen_Gormley)\
**Post date:** [May 13, 2021, 4:38pm UTC](https://connect.superhuman.com/t/date-format-not-recognised/23411/1 "2021-05-13T16:38:25Z")

</div>

Hey everyone,

I am copy and pasting data from a google sheet into a Coda table and the date formats for some of the entries are recognised and for others aren’t. Unfortunately I can’t share the doc itself as it contains confidential information. Any help would be greatly appreciated,

Thanks everyone

![image](https://global.discourse-cdn.com/coda1/original/3X/c/b/cb6b3b049ec7d63f2323c5a5774cb20aae83dbb6.png)

---

<div class="post-metadata">

**Author:** ![Scott\_Collier-Weir](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/scott_collier-weir/32/29677_2.png) [@Scott\_Collier-Weir](https://connect.superhuman.com/u/Scott_Collier-Weir)\
**Post date:** [May 13, 2021, 5:40pm UTC](https://connect.superhuman.com/t/date-format-not-recognised/23411/2 "2021-05-13T17:40:59Z")

</div>

Hey there,

I think date columns auto-formate to mm/dd/yyy so it is recognizing inputs that start with number 1-12.

It looks like you have your dates formatted as dd/mm/yyyy. Coda can definitely support that, you just want to change the options on the column like this:

 ![image](https://global.discourse-cdn.com/coda1/original/3X/b/b/bb787cce1d84bb9dd8a49ff1b8305485af4d1c33.png)

Let me know if that helps.

---

<div class="post-metadata">

**Author:** ![Stephen\_Gormley](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/stephen_gormley/32/20903_2.png) [@Stephen\_Gormley](https://connect.superhuman.com/u/Stephen_Gormley)\
**Post date:** [May 13, 2021, 6:02pm UTC](https://connect.superhuman.com/t/date-format-not-recognised/23411/3 "2021-05-13T18:02:42Z")

</div>

Hi Scott,

Thanks for the answer but I have the format set correctly, from what I can see, any other ideas?  
 ![image](https://global.discourse-cdn.com/coda1/original/3X/8/d/8d0297a721a72a8c151c871f16c645f62d46c1ee.png)

---

<div class="post-metadata">

**Author:** ![Scott\_Collier-Weir](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/scott_collier-weir/32/29677_2.png) [@Scott\_Collier-Weir](https://connect.superhuman.com/u/Scott_Collier-Weir)\
**Post date:** [May 13, 2021, 6:08pm UTC](https://connect.superhuman.com/t/date-format-not-recognised/23411/4 "2021-05-13T18:08:18Z")

</div>

Sometimes you need to randomly just re-input the same information, don’t know why. But sometimes that works if you just re-input the exact same info @Stephen_Gormley

---

<div class="post-metadata">

**Author:** ![Stephen\_Gormley](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/stephen_gormley/32/20903_2.png) [@Stephen\_Gormley](https://connect.superhuman.com/u/Stephen_Gormley)\
**Post date:** [May 13, 2021, 6:08pm UTC](https://connect.superhuman.com/t/date-format-not-recognised/23411/5 "2021-05-13T18:08:59Z")

</div>

Thanks Scott, yeh just ended up re-inputting it. Which is fine for now but won’t be great as the table grows.

---

<div class="post-metadata">

**Author:** ![Scott\_Collier-Weir](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/scott_collier-weir/32/29677_2.png) [@Scott\_Collier-Weir](https://connect.superhuman.com/u/Scott_Collier-Weir)\
**Post date:** [May 13, 2021, 6:13pm UTC](https://connect.superhuman.com/t/date-format-not-recognised/23411/6 "2021-05-13T18:13:22Z")

</div>

You should not have to as the table keeps growing. I think it is a problem of the original input information. When you originally input the column was formatted in a different date format, and it does not automatically recognize the wrong inputs when you change the format. Now that the format is changed for dates though, it should recognize any new implants put in as the table grows.

---

<div class="post-metadata">

**Author:** ![Bas\_de\_Bruijn](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/bas_de_bruijn/32/18710_2.png) [@Bas\_de\_Bruijn](https://connect.superhuman.com/u/Bas_de_Bruijn)\
**Post date:** [May 17, 2021, 9:22am UTC](https://connect.superhuman.com/t/date-format-not-recognised/23411/7 "2021-05-17T09:22:23Z")

</div>

Hi Stephen,

I had the same issue. It’s really because Coda still doesn’t play nice with European dates and numbers. I ended up making a simple import table on a subpage.

The first columns (L to R) are where I paste the raw data from my source. Then I added some additional columns which format dates from DD/MM/YYY to MM/DD/YYY using the formula below (which was posted by @Christiaan_Huizer in this thread: [Need help creating a timestamp that doesn't change once entered like now() does - #4 by Christiaan\_Huizer](https://connect.superhuman.com/t/need-help-creating-a-timestamp-that-doesnt-change-once-entered-like-now-does/21015/4) ):

 ![convert date formula](https://global.discourse-cdn.com/coda1/original/3X/2/a/2a797cb4c07af4861336382d6ae751b49feec96f.jpeg)

and another column which converts European numbers (with a comma ) to US number (with a period) using the `Substitute` formula.

Then add a button with RunActions:

- 1st action adds a row for every entry in the import table (using the custom columns as data sources)
- 2nd action deletes the row from import table afterwards

Additionally you might want to built in a check to determine if the data you are about to import already exists in the target table (checkbox column with a `If` and `Filter` formula)

It might take you 20 minutes to built or so, but it saves you a lot of time whenever you need to import data. The button action is executed smoothly and it cleans up after itself with the `DeleteRow` action, so it’s always ready for a new batch.
