Budibase does not store calculated timestamps at datetime Mysql column fields after update to 3.9.5 (or 3.10.0)

[gmentzik]

Hi devs,

We are using Budibase self host for our application. We have created Apps with Budibase since 2 years and we are using Mysql for database and till now we did not have issue saving timestamps to Mysql the way we did. We are using Budibase 3.2.46 and we decided to go for an update to latest since there many new features and optimizations. However we fall immediately to following problem.
At many of our Mysql tables we have 2 datetime columns to keep track of data modification that are updated by Save Row action.

• The one strores the server utc time (Budibase host and Mysql are located on same server but Budibase does not provide a way to get server time as far as I know, so we use Mysql server time.)
• The second one stores FE (user) UTC timestamp.

Here is how save row is structured:
Save row:

Server timestamp if fetched with a custom Mysql Server timestamp Query:
Custom query:
SELECT DATE_FORMAT(UTC_TIMESTAMP,'%Y-%m-%d %H:%i:%s') as utc_datetime;
Returns:
{
"utc_datetime": "2025-05-07 10:20:35"
}

At Save row action the timestamp field values to be stored are calculated as follows:
Last_modified_datetime_utc_db: {{ Action 1.Query result.data.0.utc_datetime }}
Last_modified_datetime_utc_fe: {{ date now "YYYY-MM-DD HH:mm" "UTC" }}
Purpose:
Store server(db) and fe (user browser) utc timestamps at Mysql table. Columns are datetime fields (basically timestamps without timezone).

When press Save button, we can see the calculated values at request payload from browser console:

Result: However timestamps Mysql table row is not updated correctly. Datetime columns remain empty in db. Seams no data is send in mysql query. I assume they are empty from the error message that field cannot be empty in cases where field value is set to required in DB.

I cannot identify the Budibase version current implementation stopped working but it is in the last 5,6 months. Please advice. I would like to avoid reimplementing the solution or applying workarounds as there many save buttons in the app. Moreover current solution worked without issue for more than a year (since Budibase 1.xx).

Thank you

[IchthysMaranatha]

Your issue might be related to this #16072.
You can either save after converting to full iso date string or save to text fields in the db or change the code as mentioned in last comment

[raventechsaigon]

We have similar issue with MySql
The SAVE ROW, CREATE ROW action does not record timestamp.
MUst use explicit query after this update.

[mikesealey]

Hey @gmentzik - It might have been better to raise this as an issue rather than a discussion.

There has been a lot of work taking place lately with dates, which has tightened up what can be passed and accepted as a date in Budibase, in order to resolve a host of bugs that arose from this previously being too loose.

Please update to the latest version (currently 3.12.2) and check to see if the issue is resolved. If you're still experiencing this issue, please create an app that demonstrates the issue (that contains nothing else), and create an issue here, and upload both the app-export demonstrating your issue, as well as an SQL CREATE script so that we can test and fix the issue.