Organizations and data
Edit output data in Duaer
In Duaer, edit a node’s output in the JSON view so you can test edge cases without resending data from an external system.
Output editing is for development only. Production executions do not use the edited copy. You are changing the editor copy, not a past execution stored in history.
Edit output data
- Run the node to load data.
- In the OUTPUT view, select JSON.
- Select Edit.
- Change the items in place. Each item still needs json. Do not hand-write files into binary.
- Select Save. Duaer saves your changes and pins the data.
Keep the shape later steps expect
If the next step reads {{ $json.customerId }}, renaming or deleting that key makes the expression empty. Keep nested objects at the same depth, so address.city stays inside address.
The number of items also changes how many times a later per-item node runs. See How items link.
[
{
"json": {
"customerId": "c-18",
"status": "past_due"
}
}
]Questions
What happens when you save edited output?
In Duaer, edit in the OUTPUT JSON view and Save pins the edited data. Later manual runs in the editor use that copy until you Unpin. History executions are unchanged.
What shape must edited output keep?
In Duaer, every item still needs json. Keep field names and nesting that later expressions read. Changing the item count changes how many times later per-item nodes run.
In this section
Pin data in Duaer
In Duaer, during development, pin a node’s output so later tests reuse that data instead of fetching fresh data.
DataUnderstand Duaer’s data structure
Understanding how Duaer structures and passes data between nodes is fundamental to building workflows. This guide covers the data structure format and how data flows.
DataUse the UI mapper in Duaer
In Duaer, data mapping means referencing data from previous nodes. It does not include transforming that data.