Compare

The Compare node detects changes between two data tables inside a dataflow. It compares a previous result set or flow branch with the latest retrieved tables from the dataflow and determines which rows are new, updated, or removed. When executed, the node performs a row-by-row comparison based on the configured columns and enriches the output with a RowState value.

Configuration

Setting	Type	Required	Description
First	Select	Yes	The first table to be compared: serves as the baseline against which the second table is compared.
Second	Select	Yes	The second table that will be compared against the first table.
Columns	Select	No	The columns to compare between the tables. If no columns are selected, the node compares all columns.
Row state column	Text	No	The column name used to store each row’s comparison state.

Click the Configure button in the property panel to define which columns should be used for the comparison: these can be bound if needed. The Configuration screen also lets you filter bindings, sources and targets.

Typical execution flow

• A Daily Trigger activates the flow.
• An import node retrieves data from an ERP or database.
• The imported data lands in a resultset holding the newest data.
• The Compare node compares the new incoming data with the previous data.
• A Not Empty node filters so only new or changed rows from the Compare node continue.
• The new or changed data is exported, e.g. to vPlan.
• A Query node retrieves all data from the first resultset (with the new data).
• That data is written to a new resultset called “previous data”, ready for the next run.

References

• Not empty node
• Any2Info DataHub Guide