# Some paths in report show t\_stamp when using tall return format

**URL:** <https://forum.inductiveautomation.com/t/some-paths-in-report-show-t-stamp-when-using-tall-return-format/41364>\
**Category:** Ignition\
**Created:** [December 9, 2020, 11:15pm UTC](https://forum.inductiveautomation.com/t/some-paths-in-report-show-t-stamp-when-using-tall-return-format/41364 "2020-12-09T23:15:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [December 9, 2020, 11:15pm UTC](https://forum.inductiveautomation.com/t/some-paths-in-report-show-t-stamp-when-using-tall-return-format/41364/1 "2020-12-09T23:15:42Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/f/1f65af2084a0f7726f89b0ecc45546201acd5bd4.png)  
I have my tag historian query setup as above. It generally does what I want it to do (all tag changes in the order that they occurred). For some reason some of the events will have the path ‘t\_stamp’. Removing different data keys causes some of these to disappear. Does anyone know why this is occurring?  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/a/fa119c48e798facbf75c1e1c2a36d92eca7a9023.png)
