Hi. All of a sudden, one of my pages throw “Invalid form One or more fields contain invalid values” when trying to update a field. The data is “Get single row”, and the row ID is passed through Data source - ID. I have also tried passing the row ID with URL parameter, but no luck. The form is only one field without any validation. I have tried a select field and a text field and get the same error. The page was working fine until this happened and I haven’t changed anything. Any ideas how I can resolve this? I’m suspecting a bug.
I’m having the same issue with a previously working Application Builder page.
There were no changes to the application or the database structure between the last time it worked, and now.
The backend appears to be returning a 500 error for my form submission – Server Error (500)
I’d say this looks like a Baserow issue given that the accept headers for me are application/json
XHRPOST
https://api.baserow.io/api/builder/workflow_action/156864/dispatch/
[HTTP/2 500 881ms]
<!doctype html>
<html lang="en">
<head>
<title>Server Error (500)</title>
</head>
<body>
<h1>Server Error (500)</h1><p></p>
</body>
</html>
I think the “Invalid form” error is a generic toast that gets thrown up on an error, not one specific to form validation
Thank you for joining here and providing more details! I guess we’ll have to wait for someone from Baserow to comment.
Correct, it is just a note that something has gone wrong. You should be able to get the details through the inspector of the browser.
- Open your browser inspector
- Select the network tab
- Submit your form
- Check the dispatch method that colours red
- Check the response. This contains the error.
There have been some updates with the choice element and row selector element for the 1.28 version. So it might be possible that this has broken existing functionality.
I did paste the response from the dispatch on the form that is having issues - an HTML body 500.
Not a very informative error
Are there any more debug steps? It looks like the page is now submitting all elements even those from other form groups on a submit - was this a recent change?
Good morning @patrick & @ethicalemu, please accept my apologies for the inconvenience, we recently introduced a bug in the create and update row workflow actions. A fix is in progress and we hope to have this deployed soon.
Cheers,
Peter Evans
Hello again @patrick and @ethicalemu.
This is being fixed at the moment, but won’t be deployed to baserow.io for a few days. We believe the issue is most often triggered by using a single or multiple select in your create/update row form.
If you would like to keep using the create/update row forms over the next few days, we recommend giving the form input no value for the single/multiple select, or disabling the input altogether by clicking “Disable field”.
I hope this helps, my apologies again, we hope to have this resolved soon.
Cheers,
Peter Evans
Hmm. While I am updating the single select field on a table, the form does not actually have this as input. I have 2 buttons, one that updates the single select to a fixed value “Flagged” and the other that updates the single select to the value of “Accepted”.
Is there another change I can make to this form to make it work? Having it not update the single-select isn’t acceptable, that is the whole purpose of my Baserow Application pages (to change the values of this field)
I have the same use case with a single select, and my fixed value also fails. I hope this will be fixed quickly as my application is not working. I also have another big issue right now:
Hi @ethicalemu
Is there another change I can make to this form to make it work?
At the moment the single select and multiple select fields won’t work in a create or update row workflow action, we hope to have our fix deployed to baserow.io soon.
In the meantime as suggested to make the actions execute, you will need to either:
- Remove the single/multiple select value from the create/update row form field, or
- Disable the field altogether from the dropdown:
Please accept my apologies again for the inconvenience, we’ll have it resolved soon.
Cheers,
Peter Evans
Hi @picklepete
Are there any updates on when Baserow will fix this issue?
Hi @patrick!
We have found a fix, and we hope to deploy it to baserow.io within the next ~48 hours.
Thank you both for your understanding!
Cheers,
Peter Evans
1 Like
Good morning @patrick & @ethicalemu!
Thanks again for your patience, the fix has been released to baserow.io. If you have any trouble with single/multiple selects in your create and update row actions, please let us know!
Cheers,
Peter Evans
The changes are being made to the record now by my application, but the form is still showing an error.
https://api.baserow.io/api/builder/domains/published/data-source/95885/dispatch/
Status
400
I’m getting a 400 now with this error response:
{
"data_source":{
"element":[
"A data source can only dispatched with an element if it is a collection element."
]
}
}
Hi @picklepete
The fix seems to work on one of my applications, but another one still has the same issue:
There are two forms loaded on this particular page in the application, and they are being shown two different users based on their role.
Another thing - after you implemented your fix (and after I publish any changes to our applications), I had to help all our logged in users clearing their cookies to be able to log back in. I guess this is related to this issue:
Hi @patrick,
I’ll need some more information here, the working application contained single/multiple selects right? Is there anything different about this non-working application?
Cheers,
Peter Evans
@patrick did you see an error with your users? Or was it a blank page?