# Transaction group, UTC tstamp when the Gateway is EST

**URL:** <https://forum.inductiveautomation.com/t/transaction-group-utc-tstamp-when-the-gateway-is-est/85972>\
**Category:** Ignition\
**Created:** [February 19, 2024, 8:08pm UTC](https://forum.inductiveautomation.com/t/transaction-group-utc-tstamp-when-the-gateway-is-est/85972 "2024-02-19T20:08:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zach\_Larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zach_larson/32/54388_2.png) [@Zach\_Larson](https://forum.inductiveautomation.com/u/Zach_Larson)\
**Post date:** [February 19, 2024, 8:08pm UTC](https://forum.inductiveautomation.com/t/transaction-group-utc-tstamp-when-the-gateway-is-est/85972/1 "2024-02-19T20:08:01Z")

</div>

How do you make your tstamps in a transaction group show in UTC instead of EST if your gateway is set for EST?

---

<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:** [February 19, 2024, 8:20pm UTC](https://forum.inductiveautomation.com/t/transaction-group-utc-tstamp-when-the-gateway-is-est/85972/2 "2024-02-19T20:20:21Z")

</div>

In the designer? You don't. (Everything in the designer uses the designer's time zone, pretty much.)

Clients will use the project timezone setting to translate timestamps naïvely displayed there (depending on the component, in Perspective).

Beyond that, you would be responsible for rendering timstamps to strings with forced time zone conversions. See this Perspective topic for techniques:

> [@Ignition Perspective Page to show the client System date and time](https://forum.inductiveautomation.com/t/ignition-perspective-page-to-show-the-client-system-date-and-time/73265/8):
>
> Sure. I recommend [DateTimeFormatter.ofPattern()](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/format/DateTimeFormatter.html#ofPattern(java.lang.String)). But I would move the complexity to a project script module with a DateTimeFormatter instance with your preferred pattern saved as a top level variable. Like so, perhaps: from java.time import ZoneId from java.time.format import DateTimeFormatter defaultFormatter = DateTimeFormatter.ofPattern("YYYY-MM-dd HH:mm") def zonedFormat(ts, zoneid, format=None): formatter = defaultFormatter if format is None else DateTimeFormatter.ofPattern(format) r…

Of course, if your transaction groups are storing into tables whose `t_stamp` columns are discarding timezone information, you may be screwed.