Parameters got lost/undefined in Edit Fields (set) node

Describe the problem/error/question

I reopend and executed a workflow today that was fine yesterday and didn’t work today. Looking into it I found that in the Edit Fields node only one of all the fields was ok but the other showed “undefined”. As can be seen from the screenshot, the green field uses the same reference as the red fields.

  1. I can rebuild this by reassigning fields but of course this shouldn’t happen?
  2. Nothing goes to the error branch - why is that? What would be an error?

What is the error message (if any)?

undefined or other errors based on trying js code on undefined values.

Please share your workflow

Share the output returned by the last node

No output because of missing data.

Information on your n8n setup

  • n8n version: 1.110.1
  • Database (default: SQLite): default cloud
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default for n8n cloud
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: mozilla on win

you have single quote and double quote both when defining variables
remove one it will work:

If you find my response helpful please mark it as solution :slight_smile:

1 Like

Moreover, you should not use the quotes in the variable names.

Make a note, also, that the error branch for Edit Fields node doesn’t make much sense. As undefined fields will not raise an issue. If you want to check for non-existing fields, use IF node before the Edit Fields one.

1 Like

Thank you moosa, I didn’t notice. Actually I dragged all the fields which makes me wonder why n8n does this if it leads to such problems. The only remaining mapping that worked was one with “‘ as well. But you’re right nonethe less. Removing one of the quotes restored the mapping.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.