# Perspective Table Selection Date Format Differs

**URL:** <https://forum.inductiveautomation.com/t/perspective-table-selection-date-format-differs/100674>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [January 9, 2025, 5:56pm UTC](https://forum.inductiveautomation.com/t/perspective-table-selection-date-format-differs/100674 "2025-01-09T17:56:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jake\_Bottari](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@Jake\_Bottari](https://forum.inductiveautomation.com/u/Jake_Bottari)\
**Post date:** [January 9, 2025, 5:56pm UTC](https://forum.inductiveautomation.com/t/perspective-table-selection-date-format-differs/100674/1 "2025-01-09T17:56:07Z")

</div>

Hello!

I'm working with a table that has 2 date columns that I would like to use the selection data to filter further data. The problem I am having is that the table itself formats the date correctly:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/d/bd7c432ecbfdcad90340af74a03c55288005b69f.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/a/9aa7af693ff0bdca25e4207175181fdb7d51d6f5.png)

However, when selecting this row, the date is changed to its string equivalent (Selection data prop):

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/b/4b1902e93a843cc6f56fd5b95c57fe51f7d287a9.png)

I can't use this format directly in things like tag history queries. So is there a way to convert this string back to a standard "date" object, or force the selection to match the underlying data?

Thanks!

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 9, 2025, 6:02pm UTC](https://forum.inductiveautomation.com/t/perspective-table-selection-date-format-differs/100674/2 "2025-01-09T18:02:37Z")

</div>

Include a row ID in your table, in a hidden column if necessary. Use that to access the correct row of the raw table data.

---

<div class="post-metadata">

**Author:** ![Jake\_Bottari](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@Jake\_Bottari](https://forum.inductiveautomation.com/u/Jake_Bottari)\
**Post date:** [January 9, 2025, 6:05pm UTC](https://forum.inductiveautomation.com/t/perspective-table-selection-date-format-differs/100674/3 "2025-01-09T18:05:53Z")

</div>

If going that route, wouldn't it make sense then to just reference the selected row number and use the data from the table at that row?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 9, 2025, 6:07pm UTC](https://forum.inductiveautomation.com/t/perspective-table-selection-date-format-differs/100674/4 "2025-01-09T18:07:45Z")

</div>

Yes, unless you are allowing multiple row selection. That only works with selection data.

---

<div class="post-metadata">

**Author:** ![Jake\_Bottari](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@Jake\_Bottari](https://forum.inductiveautomation.com/u/Jake_Bottari)\
**Post date:** [January 9, 2025, 6:09pm UTC](https://forum.inductiveautomation.com/t/perspective-table-selection-date-format-differs/100674/5 "2025-01-09T18:09:20Z")

</div>

True. Seems like an unnecessary workaround and the selection data should follow the formatting from the underlying data/column config. Thanks!

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 9, 2025, 7:12pm UTC](https://forum.inductiveautomation.com/t/perspective-table-selection-date-format-differs/100674/6 "2025-01-09T19:12:54Z")

</div>

It is making a round trip to the browser, where the actual row selection happens. JSON is not perfectly reversible for some types.
