Organizations and data
Reference a previous field from the input panel
The input panel lists fields earlier nodes have already produced. Drag a field into a parameter and Duaer inserts an expression that points at that item. The drag is a reference. It does not freeze the value or change the data.
Where input-panel field names come from
The input panel can list fields only after earlier nodes have run, or after you have pinned their output. If nothing has run and nothing is pinned, the panel is empty. That does not mean this node has no input.
The list is field paths, not a new copy of the data. customerId and address.city both come from json on the previous item.
Drag a field into a node parameter
- Open the node you are filling in and check that the input panel shows the previous step.
- Drag the field into the parameter and release.
- The field becomes an expression such as {{ $json.customerId }}. Picking the same field inside the expression editor does the same thing.
This only writes the path into the parameter. It does not filter, rename, or reorder items. To change the data, edit the output, or use a node that returns new items.
A correct field path can still fail item linking
The expression uses .item to find the input row that belongs to this output row. When the counts no longer match, or a Code node returned new items without saying which input they came from, a dragged field fails at run time with a linking error.
Read How items stay linked through a run, then Errors when items are not linked. Changing the field name does not fix a missing link. The path can be right and the item still unmatched.
Questions
Where do the field names in the Duaer input panel come from?
Field names in the Duaer input panel come from data earlier nodes have already produced, or from output you pinned on those nodes. If nothing has run and nothing is pinned, the panel is empty. The list is field paths, not a new copy of the data.
Does dragging a field into a Duaer parameter change the data?
In Duaer, dragging a field into a parameter only writes an expression path, such as {{ $json.customerId }}. The drag does not filter, rename, or reorder items. If the items are not linked, the expression still fails at run time with an item-linking error.
In this section
How data is shaped between nodes
In Duaer, what one node hands to the next node is a list of items. On each item, ordinary fields live in json and files live in binary. Later nodes walk the items one by one.
DataEdit the data in a node output
You can change a node output in the JSON view. After you save, the edited data is pinned on the node, and later steps in the editor read that version.
DataHow items stay linked through a run
Each output item remembers which input item it came from. .item in an expression follows that link backward. A one-to-one list, a one-to-many list, or a reorder can be linked automatically.