# Table Export to CSV Time Issue

**URL:** <https://community.fibery.io/t/table-export-to-csv-time-issue/2302>\
**Category:** Misc\
**Created:** [December 8, 2021, 7:02pm UTC](https://community.fibery.io/t/table-export-to-csv-time-issue/2302 "2021-12-08T19:02:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![luke\_Irvine](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/luke_irvine/32/4428_2.png) [@luke\_Irvine](https://community.fibery.io/u/luke_Irvine)\
**Post date:** [December 8, 2021, 7:02pm UTC](https://community.fibery.io/t/table-export-to-csv-time-issue/2302/1 "2021-12-08T19:02:19Z")

</div>

When exporting a table to a CSV file the times in a Date Range are changing, they are going foward 5hrs compared to what I have in my table. I need these times to not change.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/4417eeb4d41542523e5f6ed38905adefc7696b98.png)

---

<div class="post-metadata">

**Author:** ![Sergey\_Truhtanov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sergey_truhtanov/32/13986_2.png) [@Sergey\_Truhtanov](https://community.fibery.io/u/Sergey_Truhtanov)\
**Post date:** [December 9, 2021, 9:28am UTC](https://community.fibery.io/t/table-export-to-csv-time-issue/2302/2 "2021-12-09T09:28:18Z")

</div>

That is because we store dates in UTC, and convert to local timezone on UI.

> **[Timezones](https://help.fibery.io/en/articles/5499837-timezones)**
>
> See how timezones \[do not\] work in Fibery and how to handle it in Formulas, Automations, Reports and etc.

Person from another timezone will see those DateRange values converted to his timezone.  
Export outputs dates in UTC.  
We could probably add a setting whether to export in UTC or local timezone. But I’m not sure, we need to discuss that.

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [December 9, 2021, 3:45pm UTC](https://community.fibery.io/t/table-export-to-csv-time-issue/2302/3 "2021-12-09T15:45:57Z")

</div>

It seems like a helpful setting for the average no-code user

---

<div class="post-metadata">

**Author:** ![luke\_Irvine](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/luke_irvine/32/4428_2.png) [@luke\_Irvine](https://community.fibery.io/u/luke_Irvine)\
**Post date:** [December 9, 2021, 5:07pm UTC](https://community.fibery.io/t/table-export-to-csv-time-issue/2302/4 "2021-12-09T17:07:59Z")

</div>

Or a setting to lock the times to a static value would be great.

I don’t even want them to change if I change time zones. I set the values in there for each event we are doing and I expect them not to be adjusted at all.

---

<div class="post-metadata">

**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:** [December 9, 2021, 8:34pm UTC](https://community.fibery.io/t/table-export-to-csv-time-issue/2302/5 "2021-12-09T20:34:03Z")

</div>

For a workspace where all users are in the same time zone, then yes, it makes sense to just ignore time zone corrections in general. But for workspaces where users are spread out it is not optimal.  
And having two different types of date-time fields (static and dynamic) would probably be worse than Sergey’s suggestion of allowing the export to be UTC or local (which may itself be a UX degradation for the majority of users ☹ ).