Announcements
The Google Cloud Community will be in read-only from July 16 - July 22 as we migrate to a new platform; refer to this community post for more details.

It records correctly in the database, but the time appears +3:00 from the date of release

Hello everyone, I don't know if you've ever had this type of problem, which is the second time it's happened. I enter the date and time in the database, and it saves correctly in the database, however, when it appears in the appsheet it's 3 hours ahead. I need to solve this!

Solved Solved
0 5 211
1 ACCEPTED SOLUTION

I found the error. In the gateway when placing a dateTime column it needs to be set as "without Zone", the record saves correctly, but the return compares the Bank Zone with the Appsheet and in my case it appeared in the Appsheet +3:00

View solution in original post

5 REPLIES 5

What data source are you using?

I'm using Cloud Database for Postgres.
My record is correct in the Database, but in the preview it says +3:00

This is happening because there was an update in Postgres that changed the behavior. Please contact AppSheet support with this.

in postgres it shows the time I recorded, but in appsheet it shows +3:00

I found the error. In the gateway when placing a dateTime column it needs to be set as "without Zone", the record saves correctly, but the return compares the Bank Zone with the Appsheet and in my case it appeared in the Appsheet +3:00

Top Labels in this Space