Last updated:
Not Empty
The Not Empty node evaluates the result set of a previous node (most commonly a Compare node) and determines whether the dataflow should continue based on the selected result type.
Configuration
Section titled “Configuration”Defines which subset of the previous node’s result is evaluated for emptiness.
| Setting | Required | Description |
|---|---|---|
| Default | Yes | Uses the default output of the previous node. |
| All | No | Evaluates all records, regardless of change status. |
| New | No | Evaluates only records that did not exist in the previous comparison run. |
| Changed | No | Evaluates only records that existed before but have changed. |
| Deleted | No | Evaluates only records that existed before but are no longer present. |
| New or changed | No | Evaluates records that are either new or modified. This is the most common option for incremental processing. |
| New, Changed or Deleted | No | Evaluates any type of difference detected. |
| Unchanged | No | Evaluates records that are identical to the previous run. |
When to use it
Section titled “When to use it”The Not Empty node is most commonly placed directly after a Compare node, to prevent downstream processing when no relevant changes are detected.
- Use Input result = New or Changed for standard incremental dataflows.
- Avoid using Unchanged unless explicitly validating stable datasets.