I am configuring a “next page” form node, where I specify form fields in json format. The problem is that even if I declare fieldName and fieldLabel, I don’t get node results (output) with fieldName.
Hi @inssaf!
From your screenshots, nothing is wrong with your JSON. The Next Form Page node won’t show output when you click "Execute step” because it only defines the form structure. You’ll only see the field values using “fieldName” after you submit the form through the Test or Production URL and then check the full workflow execution.
Looking at your screenshot the output is actually coming back with "type something": "hi" which is the fieldLabel, not "typesometing" which is what you set as fieldName. So the node is ignoring your fieldName and falling back to fieldLabel as the output key, that’s a bug. The JSON mode for the Form node has had a few rough edges like this, I’d recommend opening an issue on the n8n GitHub repo at GitHub · Where software is built since there have been similar reports around JSON-defined form fields not behaving correctly. In the meantime you could work around it by just setting your fieldLabel to whatever key name you actually want in the output, not ideal but it should unblock you.
Hello @tamy.santos thanks for the reply! yes I’m talking about the output after form submission. Normally FieldName is what is used in the output of the Form node and to reference the field in expressions, and fieldLabel is the label that appears above the input field on the rendered form.In my example, I want that “type something” to be the label and “typesomething” to be the name reference of that field. but after execution, the workflow is referencing to that field by the label name instead of the fieldName as shown in the screenshot.
I didn’t see the their reply this weekend until this morning but it was too late, issue closed. So I’ll keep waiting here to see if there’s someone else encountering the same problem.
