# T\_stamp format of historian **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [January 20, 2023, 10:24am UTC](https://forum.inductiveautomation.com/t/t-stamp-format-of-historian/68837 "2023-01-20T10:24:22Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [January 20, 2023, 12:53pm UTC](https://forum.inductiveautomation.com/t/t-stamp-format-of-historian/68837/3 "2023-01-20T12:53:24Z")
This is an Excel issue, not an Ignition issue. That said, Excel is very, _very_ bad at this. EDIT: Phil beat me to that point. Unfortunately, even using the built-in functions, Excel rarely uses a useful format. I updated this function to allow an arbitrary date format, or use the deafult 'yyyy-MM-dd HH:mm:ss'. > [@Copying an Excel file to a table's dataset](https://forum.inductiveautomation.com/t/copying-a-excel-file-to-a-tables-dataset/34942/7): > > The [Apache POI](https://poi.apache.org/apidocs/4.1/index.html) libraries are included with Ignition. At the time I was only needing to read files, so xlrd was all that was necessary. I'm just starting to dig into POI, myself, but here's a start: EDIT 2021-08-23: Updated to allow JsonDataSets. Changed to allow for a ByteArray output instead of writing to a file. EDIT 2023-01-20: Added option for date formats. Default is 'yyyy-MM-dd hh:mm:ss'. EDIT 2023-05-12: Added options for first row and column, if needed to offset from A1 def datasetT… --- _[View the full topic](https://forum.inductiveautomation.com/t/t-stamp-format-of-historian/68837)._