Organizations and data
Errors when items are not linked
When an expression cannot find the matching input item, or finds more than one, the run stops on that expression. Point at a specific item, or set the link in code.
The expression cannot find a matching input item
The message says the previous node has no information for this expression. The usual cause is a Code node that built new items without pairedItem, or a step in the middle that changed the count so the rows no longer line up.
If you only need one specific row, stop using .item. Use .first(), .last(), or .all() with an index. Indexes start at 0.
{{ $("Customers").first().json.email }}
{{ $("Customers").all()[0].json.email }}One output item matches more than one input
Summarize, Aggregate, and Merge fold many items into one, or combine branches. The resulting item has several inputs behind it, and .item cannot choose.
Use first, last, or an index on all, and name the row you wanted from before the fold. If the work really is one output per input, do not fold first and then reach back for a single field. Read the field before the summary.
A different field name will not hide this
A field still listed in the input panel only means that step once output that name. The error says the link between items broke. Replacing {{ $json.email }} with another field still uses .item, so the error stays.
When a single item came in, Duaer can point every later item at it. A sample with one item can succeed in the editor and fail in production when many items arrive. Run again with the same count production uses.
Questions
Why does Duaer say the previous node has no information for an expression?
Duaer says the previous node has no information for an expression when a Code node built new items without pairedItem, or a step in the middle changed the item count so the rows no longer line up. If you only need one row, replace .item with .first(), .last(), or .all() plus an index. Indexes start at 0.
Does changing the field name fix an item-linking error in Duaer?
Changing the field name does not fix an item-linking error in Duaer. A name still listed in the input panel only means that step once output it. The error means the link between items broke. After Summarize, Aggregate, or Merge folds many items into one, .item can also fail because several inputs sit behind that one item.
In this section
How 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.
DataMark item links in the Code node
When a Code node returns new items, set pairedItem on each one so later expressions know which input it came from. Without that, .item reports that the items are not linked.
DataReference 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.