Current timestamp incorrect

[rsnell]

In one of my apps, I'm populating a timestamp field with nabCurrentTimeStamp when a button is pressed. However, the time is 4 hours ahead of the system time. Any thoughts?

[Johnny Major]

When you say "system time," are you referring to the IBM i? If so, nabCurrentTimeStamp represents the current time of the local device running the application, not the current time on the IBM i.

[rsnell]

It's also wrong if it's the device time. We're using Chromebook to deliver the app.

[rsnell]

I did more testing. The timestamp is retrieved correctly using the March release of Valence 6.3, but is incorrect in the May version. It looks like the May version is picking up UTC time

[robert.swanson]

Thanks for the info, we're looking into it.

[robert.swanson]

This should be resolved in the latest build (6.3.20250708.0)

[rsnell]

That's great!