# CSV exported losing timezone setting
**URL:** https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004
**Category:** Kibana
**Created:** [April 22, 2021, 7:22pm UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004 "2021-04-22T19:22:13Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@marcosvrrs](https://discuss.elastic.co/u/marcosvrrs)
#### Post date: [April 22, 2021, 7:22pm UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/1 "2021-04-22T19:22:13Z")
Hi all,
Our kibana 7.12 started to show this behaviour (we are using Elastic Cloud).
The dashboards show the timestamp formatted correctly as the Advanced Settings were chosen to be America/Sao\_Paulo.
So the dashboard usually had a row with timestamp 15h00, and the JSON was in UTC (18h00). When we exported the CSV it came correctly as 15h00.
Now when we export the CSV it keeps with the UTC date.
We already rebooted Kibana, and tried to change the timezone in the Advanced Settings to "Browser" and to "America/East" to see if there is any change, but the timestamp keeps showing in UTC when we export the CSV.
---
### Author:  [@Marta\_Bondyra](https://discuss.elastic.co/u/Marta_Bondyra)
#### Post date: [April 23, 2021, 9:33am UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/2 "2021-04-23T09:33:03Z")
Hi @marcosvrrs, could you post the exact steps to reproduce here? I tried to export a datatable from Dashboard to CSV, but it works correctly for me.
---
### Author:  [@marcosvrrs](https://discuss.elastic.co/u/marcosvrrs)
#### Post date: [April 23, 2021, 3:11pm UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/3 "2021-04-23T15:11:18Z")
Hi @Marta_Bondyra , thanks for the reply!
So, first we have a dashboard like this:
Then I go over the 3 dots, select more, and select "Download CSV" :
And the exported CSV with the 3 hours difference:
Sorry for the blurred images. Hope you can understand.
---
### Author:  [@marcosvrrs](https://discuss.elastic.co/u/marcosvrrs)
#### Post date: [April 23, 2021, 3:31pm UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/4 "2021-04-23T15:31:08Z")
@Marta_Bondyra I tried with a saved search through discover, and the exact same thing happens. So, both ways the same issue shows.
---
### Author:  [@Marta\_Bondyra](https://discuss.elastic.co/u/Marta_Bondyra)
#### Post date: [April 23, 2021, 3:37pm UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/5 "2021-04-23T15:37:52Z")
Thanks, finally I was able to reproduce it in 7.12. Looks like it is fixed for the upcoming version 7.13, but I'll go through the list of our issues and see if we plan to merge a fix for 7.12.2.
---
### Author:  [@marcosvrrs](https://discuss.elastic.co/u/marcosvrrs)
#### Post date: [April 23, 2021, 3:47pm UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/6 "2021-04-23T15:47:45Z")
@Marta_Bondyra thanks for the reply. When is this fix coming? Do you have an expected day of the release? It has broken a few scripts that are critical for our daily routines.
(this 7.12 version is so painful. We caught a MAJOR bug in the 7.12 few weeks ago and had our cluster offline until the elastic dev team fixed in 3 patches)
---
### Author:  [@Marta\_Bondyra](https://discuss.elastic.co/u/Marta_Bondyra)
#### Post date: [April 23, 2021, 4:52pm UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/7 "2021-04-23T16:52:26Z")
I'm really sorry to hear it!
Unfortunately, I cannot give you exact date of the release, but it will be released in about a month. Seeing how critical it is for you, I will try to advocate also for releasing this fix for 7.12.2 (which will happen much sooner).
Sorry one more time and thank you for your patience.
---
### Author:  [@Marta\_Bondyra](https://discuss.elastic.co/u/Marta_Bondyra)
#### Post date: [April 26, 2021, 8:14am UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/8 "2021-04-26T08:14:48Z")
Hi @marcosvrrs,
I found out about workaround: in the index pattern, the date field needs explicit formatting as `date` .
1. Open the index pattern, find the date field
2. Click the pencil on the field row
[](https://user-images.githubusercontent.com/908371/112195457-38a4a880-8bc7-11eb-9624-8453eb01fc68.png)
3. Set format to Date
[](https://user-images.githubusercontent.com/908371/112195505-45290100-8bc7-11eb-8e1a-f5b4e589c763.png)
After setting the date format, the index pattern field list will show `Date` under the `Format` header, as shown in the first screenshot.
4. In the CSV export, this field will be formatted correctly and use the correct time zone:
[](https://user-images.githubusercontent.com/908371/112196055-dd26ea80-8bc7-11eb-8904-83d3f3b3b47d.png)
This is happening because the "default" field formats are not being applied due to a bug. Just like I mentioned, this will be fixed in 7.13 with [elastic/kibana#88303](https://github.com/elastic/kibana/pull/88303)
---
### Author:  [@marcosvrrs](https://discuss.elastic.co/u/marcosvrrs)
#### Post date: [April 26, 2021, 3:12pm UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/9 "2021-04-26T15:12:11Z")
Hi @Marta_Bondyra, thanks for the workaround, it worked.
Have a nice day! 😃
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 24, 2021, 3:12pm UTC](https://discuss.elastic.co/t/csv-exported-losing-timezone-setting/271004/10 "2021-05-24T15:12:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.