Hi @ethicalemu,
The error you encountered is now fixed on baserow.io, thanks again for raising this with us!
Cheers,
Peter Evans
After some testing I got the form to work. I’m not completely sure what was wrong, but I suspect that I might have made a mistake using a form input from the first form on the page for the action update on the second form. Anyway, it works fine now so thank you for fixing this quickly!
1 Like
@jrmi It’s blank page
Great! This problem seems to be fixed.
Now I’m back to struggling with “Reset field values after submission” on my page resulting in the field not actually capturing the value.
With the “Reset field values after submission” not checked on the form, the payload for the dispatch looks like this:
{"user":1,"data_source":{"element":947075},"data_source_context":null,"page_parameter":{},"form_data":{"947076":" ","947077":"Test submit flag"},"previous_action":{}}
Changing nothing else on the page but the “Reset field values after submission” box results in the field not being submitted on the dispatch
This is the same content being entered and the same button being clicked on the page, no changes to the events on the page when the button is clicked or the layout, literally only this one box
{"user":1,"data_source":{"element":947199},"data_source_context":null,"page_parameter":{},"form_data":{"947200":" ","947201":" "},"previous_action":{}}
I’m not sure if these problems are related, but if the Reset to default values after submission box IS checked, the data refresh and redirect events AFTER the Update Row event occur and the page loads the next result (The single-select on the field changes on the click, so the change removes it from the dataset filtered by that single-select).
If the button is not checked we get the field value on the Update Row event, but the refresh / page redirect do not happen (and I have to manually refresh the page to load the next row)
Ultimately, pretty weird behavior from a seemingly straightforward row mutation.
I’m not sure but I seem to be getting an error that is related to the tread above and its driving me nuts. After reading this thread, I have a little more idea where the problem is now, so thanks for that. It would be nice if the error message told you which field was the culprit.
When I looked into the inspector, I see the following:
“error”: “ERROR_WORKFLOW_ACTION_IMPROPERLY_CONFIGURED”,
“detail”: “The workflow_action configuration is incorrect: The result value of the formula is not valid for the field Membership (field_3152677): The provided select option value ‘’ is not a valid select option.”
That membership field was deleted from the form, and I can’t find any reference to it there now. So I disabled that field in the form event and then the error cleared, but not sure why its hanging around after having been deleted (its not referenced at all in the form event fields any more either). I have encountered this several times now, and previously the only way to clear it was to delete the entire form and build it again. Which is indeed a massive pain. 
At least now I know where to look and can disable the field.
I hope the above info might help locate and clear the root cause. Thanks.
Just to confirm this, I tried to change over another field from Choice to Record Select. This required adding a new db field for the record select. I deleted the Choice form object, and its reference in the Events area, but got the same error. Once I disabled that old field, it worked. Its like the old form Choice element is hanging around, still linked to the event, but… its not. Very strange. Definitely a show stopper the way it is. And… the Record Select doesn’t populate with its default value either, it always displays Make a Choice.
Something else to chew on with Xmas dinner. 
Thanks.
I got the same invalid form error, the issue comes from the record selector element. When I inspected on chrome, it threw this error
https://…/api/builder/workflow_action/9199/dispatch/
“The workflow_action configuration is incorrect: The result value of the formula is not valid for the field Default Shipping Address (field_5882): [ErrorDetail(string=‘This field may not be null.’, code=‘null’)]”
I found that when I checked the checkbox “Allow Multiple Values” on Record Selector Element, this error is gone.
So I suspected, the XHR request must be sending NULL instead of empty array. So I tried to debug using Postman Interceptor, and change the payload instead of NULL to empty array , and it went through with status 200 OK.
I hope the dev team can push this changes soon with the commit related to this issue.
1 Like
Awesome work, thanks for adding that, I am sure it will help the devs! Really keen to see this issue fixed now as its the only holdup for being about to complete the first draft of my app for use. 