Timestamps in Tag Historian vs Transaction Groups working differently in reports

Ignition
1

I've successfully created reports using a Tag Historian Query. I'm now trying to create a report using an SQL query. The problem I'm running into is that the t_stamp column is an integer in historical tables, but text in transaction group tables. The former is able to be formatted as a date in the reporting module while the latter just displays the unix time as a string. Now, I can format the date as desired in my SQL query, but I'd really like to make that adjustment at the cell level in the report. I've tried casting t_stamp to a double but no dice. I'm guessing the Tag Historian Query data source in reports is doing something in the background to convert the column to a date.

Am I missing something obvious here?

2

The historian's t_stamp column is milliseconds UTC. Most databases have conversion functions. (There's too much variability in branded databases' support for precision timestamps that handle timezoned data correctly. Looking at you, Microsoft.)