# Issues with reading dates for future data

**URL:** <https://forum.inductiveautomation.com/t/issues-with-reading-dates-for-future-data/76533>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [July 18, 2023, 5:23pm UTC](https://forum.inductiveautomation.com/t/issues-with-reading-dates-for-future-data/76533 "2023-07-18T17:23:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cristian\_Gomez](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cristian_gomez/32/49040_2.png) [@Cristian\_Gomez](https://forum.inductiveautomation.com/u/Cristian_Gomez)\
**Post date:** [July 18, 2023, 5:23pm UTC](https://forum.inductiveautomation.com/t/issues-with-reading-dates-for-future-data/76533/1 "2023-07-18T17:23:01Z")

</div>

Good afternoon everyone, I would like to bring up the error I'm experiencing to receive suggestions regarding the possible cause. I'm importing a dataset with multiple data formats, and two of the columns are dates. However, in the "Device Time" column of the table, a different date is being displayed compared to the original date in the dataset. On the other hand, the "Last Successful Comm" column, which has the same format, is showing the correct date.

I appreciate your contributions.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/3/c313608648481114a71ea1e6ab37f743891a743d.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/b/2bc7b88fa057346c5d24d5a1d80f9a23b7c43634.png)