# CSV import wrong date **URL:** \ **Category:** Get Help\ **Created:** [September 10, 2024, 11:17am UTC](https://community.fibery.io/t/csv-import-wrong-date/6620 "2024-09-10T11:17:39Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [September 10, 2024, 11:17am UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/1 "2024-09-10T11:17:39Z")
I tried changing the preference in Fibery but it didn’t help. My date format in the CSV is DD-MM-YYYY, but it imports as MM-DD-YYYY. It imports correctly when there is also DD’s that are over 31, then it know which is the right way. Is there a way to indicate the date format I want it to import as? ---
**Author:** ![schorsch](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@schorsch](https://community.fibery.io/u/schorsch)\ **Post date:** [September 12, 2024, 6:17am UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/2 "2024-09-12T06:17:14Z")
I might be completely wrong about specific description, or misunderstand. But afaik if you import as actual dateform or datatype that could have to do, i.e. be controlled by your user display settings: settings ► preferences ► date format? might also be related to a formatting bug or remainder in that sense. → does other order/format potentially fix your issue? ---
**Author:** ![Eren\_Turgut](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eren_turgut/32/4425_2.png) [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)\ **Post date:** [October 23, 2024, 1:40pm UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/3 "2024-10-23T13:40:55Z")
I have the exact same problem… please advice – this is a kind of a critical issue. As Ron already tried I also have the date format in the user settings set to DD.MM.YYYY (exactly as it’s formatted in the CSV) but it still imports it as MM.DD.YYYY. ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [October 23, 2024, 1:58pm UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/4 "2024-10-23T13:58:15Z")
Just as a temporary solution: add a line with a date that is over 12 on the DD section of the date, (16.03.2024) then Fibery should understand which format is the right one format to import in. Then delete that entity after import. Lmk if it works for you. ---
**Author:** ![Eren\_Turgut](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eren_turgut/32/4425_2.png) [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)\ **Post date:** [October 23, 2024, 2:16pm UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/5 "2024-10-23T14:16:40Z")
I have many lines with dates that are over 12 on the DD part, or do you mean if the **first** line has such a date then all the rest is imported correctly? Sorry I cannot try it immediately as I’ve already imported 20K+ entities and it would be a pain to redo everything (can’t bulk delete / import 20K+ entities), cleaning up manually for now. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 23, 2024, 2:34pm UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/6 "2024-10-23T14:34:32Z")
> [@Eren\_Turgut](#): > > I have many lines with dates that are over 12 on the DD part Do you mean that some entities (those with over 12 in DD) were imported as you would like and others (those with 12 and under in DD) were imported wrongly? ---
**Author:** ![Eren\_Turgut](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eren_turgut/32/4425_2.png) [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)\ **Post date:** [October 23, 2024, 3:25pm UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/7 "2024-10-23T15:25:49Z")
I believe that was the case, but some entities had empty date fields so I could be wrong and it could be that ALL those with DD 12 and above were left empty and the others imported incorrectly. ---
**Author:** ![Eren\_Turgut](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eren_turgut/32/4425_2.png) [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)\ **Post date:** [November 25, 2024, 3:43pm UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/8 "2024-11-25T15:43:57Z")
> [@RonMakesSystems](#): > > Just as a temporary solution: add a line with a date that is over 12 on the DD section of the date, (16.03.2024) then Fibery should understand which format is the right one format to import in. Then delete that entity after import. Lmk if it works for you. Can confirm this worked for me (added the line as the first line to import) ---
**Author:** ![Eva\_Folch](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eva_folch/32/11814_2.png) [@Eva\_Folch](https://community.fibery.io/u/Eva_Folch)\ **Post date:** [September 4, 2025, 9:20am UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/9 "2025-09-04T09:20:06Z")
Just in case, it might help someone. I did not manage to import the dates correctly. At the end, I imported them as Text and pasted the values in the date column in the Fibery database. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 19, 2026, 1:16pm UTC](https://community.fibery.io/t/csv-import-wrong-date/6620/10 "2026-02-19T13:16:39Z")
Now you can select date format during the import > [@February 19, 2026 / Filter by to-many relation count, many small improvements](https://community.fibery.io/t/february-19-2026-filter-by-to-many-relation-count-many-small-improvements/10411): > > Many quality of life improvements today, hope you will find something to enjoy. Filters: Filter by to-many relation count in views Until now, you couldn’t easily filter items by how many related entities they have. For example, to see Features with at least 2 Bugs, you had to first create a separate Formula field for the bug count and then filter by that formula. You can now filter directly by the count of items in a to-many relation. In filters, collections (like Bugs) now have a “Count” opti…