Save New Row in Form on Postgres Data Source

[jhill-mindex]

Checklist

• I have searched budibase discussions and github issues to check if my issue already exists

Similar issue here but much earlier version:
#10142

Hosting

• Cloud
  • Tenant ID: comida

Describe the bug
When I go to save a new row in my Postgres DB, nothing pops up on screen for an error but the row isn't inserted. I found in the developer tool logs the following Request payload:

{
"apApplicantName": "XXXXX",
"apAddress": "XXXXX",
"apCity": "XXXXX",
"apState": "XXXXX",
"apZIP": "XXXXX",
"__value": {
"apApplicantName": "XXXXX",
"apAddress": "XXXXX",
"apCity": "XXXXX",
"apState": "XXXXX",
"apZIP": "XXXXX"
},
"__valid": true,
"__currentStep": 1,
"__currentStepValid": true,
"tableId": "datasource_plus_b623bc1531d74eaa9836268104314ca6__tblapplicant"
}

with the following Response Payload:

{"status":500,"validationErrors":{"apTaxMapID":["can't be blank"]}}

When I check my Postgres table to see if apTaxMapID is not nullable it only shows that the applicantID column is not nullable, it doesn't show anything about apTaxMapID.

This was working previously and nothing was changed on my side.

Expected behavior
I would expect the save button to insert a new row into Postgres as it was previously.

Desktop (please complete the following information):

• OS: macOS Sequoia Version 15.5
• Browser Chrome
• Version 137.0.7151.120

Additional context
I was able to insert a row into Postgres directly with an INSERT statement even with a NULL apTaxMapID column

[linear]

BUDI-9495 Save New Row in Form on Postgres Data Source

[ConorWebb96]

Hey @jhill-mindex,

Is this set as required within the Budibase table UI itself?

If yes, toggle off it being required and it should resolve your issue.

[jhill-mindex]

Hi Conor, thanks for the response. I'm not using a table, I'm using a form. The strange part is that the field the error message is referring to (apTaxMapID) doesn't even exist in my form at all.

Please let me know if I can provide any other details to help troubleshoot further.

[ConorWebb96]

Hey @jhill-mindex,

Yes, even if it's not included in the form. If it's required at the table level, the request will still fail as the field can't be left blank for that table because it is required.

Can you check the base table in the data area and see if the field apTaxMapID is required? If it is, you can uncheck it, and you should be able to submit your form again.

[jhill-mindex]

So I can see that column is required but I can't toggle it off.

The primary key is a different column (applicantID)

However, I do believe at one point I changed the primary key column from apTaxMapID to applicantID. I just did a fetch table again to refresh it, but I'm still not able to toggle the required off.

I appreciate the quick responses, let me know if you need more info.

[ConorWebb96]

Hey @jhill-mindex,

Have you made any changes to your database? Was this field not nullable at one point, and then was it changed? If it's auto-detected as required, that likely means it's required/not nullable at the database level.

Do you have your Postgres schema? Please send across an example so I can have a look.

I'm going to convert this to a discussion as it's very likely to be schema-related.