# Corrupt CSV on export

**URL:** <https://forum.inductiveautomation.com/t/corrupt-csv-on-export/2971>\
**Category:** Ignition\
**Created:** [May 26, 2011, 7:43pm UTC](https://forum.inductiveautomation.com/t/corrupt-csv-on-export/2971 "2011-05-26T19:43:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joseph\_Mendonca](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@Joseph\_Mendonca](https://forum.inductiveautomation.com/u/Joseph_Mendonca)\
**Post date:** [May 26, 2011, 7:43pm UTC](https://forum.inductiveautomation.com/t/corrupt-csv-on-export/2971/1 "2011-05-26T19:43:01Z")

</div>

Every time the database is exported to a CSV the Path identifier in cell A1 is preceded by the following characters ï»¿Path. Weird characters has to be deleted in order to get a successful import from CSV.

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [May 27, 2011, 9:56pm UTC](https://forum.inductiveautomation.com/t/corrupt-csv-on-export/2971/2 "2011-05-27T21:56:53Z")

</div>

That’s the UTF-8 Byte Order Marker. Excel, which I presume you’re using to open it, has horrible UTF-8 support, from what I read online.

But, the problem is still on our side- we require the BOM for UTF-8, when the general convention is that it should be optional. But still, it’s allowed, and most text editors won’t mind it.

Regards,

---

<div class="post-metadata">

**Author:** ![Joseph\_Mendonca](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@Joseph\_Mendonca](https://forum.inductiveautomation.com/u/Joseph_Mendonca)\
**Post date:** [May 27, 2011, 10:34pm UTC](https://forum.inductiveautomation.com/t/corrupt-csv-on-export/2971/3 "2011-05-27T22:34:34Z")

</div>

I’m using Open Office Spreadsheet. Switching to Unicode UTF-8 solved the problem. Thanks
