Duaer

Organizations and data

Fix item linking errors in Duaer

In Duaer, when you use .item to reference an earlier node, the run errors if the linking thread is broken or points at more than one item.

You can reference any earlier node in the chain with syntax like $("Node name").item. Duaer follows each output item’s linking thread back to decide which row to use.

.item fails when the thread is broken, or when it points at more than one item. Avoid .item with .first(), .last(), or .all()[index], or fix the link.

Info for expressions missing from previous node

The message says the previous node has no information for this expression. A common cause is a Code node that returned new items without pairedItem, or a middle step that changed the count.

If you only need one row, stop using .item:

{{ $("Customers").first().json.email }}
{{ $("Customers").all()[0].json.email }}

In the Code node, return which input each output used. See Preserve linking in the Code node.

Multiple matching items for expression

Summarize, Aggregate, and Merge can fold many items into one. The resulting item has several inputs behind it, and .item cannot choose.

Use first, last, or an index on all, or reference a node that does not have multiple matches. If the work is one output per input, read the field before the fold.

Questions

Why does Duaer say info for the expression is missing from the previous node?

The linking thread broke—often a Code node without pairedItem, or a middle step that changed the count. If you only need one row, use .first(), .last(), or .all()[index].

What should you do when there are multiple matching items?

In Duaer, after summarize, aggregate, or merge, several inputs sit behind one item and .item cannot choose. Use first/last/all with an index, or read the field before the fold. Renaming the field does not fix linking.

In this section