Update entity record node for modifying an existing record in a Data Fabric entity from a workflow, without a connection.

Updates an existing record in a Data Fabric entity. This is a native node. It doesn't need a connection. It works with existing entities from the Data Fabric platform, wherever they are stored, and with entities defined in a VS Code solution. Entities in VS Code: how to define an entity in a VS Code solution.

The Identify record by field determines how the node locates the record to update. The two options are described below.

The panel shows the entity picker, the filter that identifies the record, and the list of fields to update.

The panel prompts you to select a Query entity records node from the workflow. The record that node located is the one this node updates.

This node doesn't support the Error handling tab.

The node's output mirrors the updated record's fields. The fields and types vary by entity and typically include the entity's standard system fields (such as Id, CreateTime, CreatedBy, UpdateTime, and UpdatedBy) alongside your custom fields. Access them downstream as $vars.<nodeId>.output.<fieldName>.

The output is a live reference to the updated record, not a stored copy of the values you wrote. Every expression, condition, or script that reads it re-reads the record at that moment, so it reflects any later change, so no extra Query entity records node is needed. The LIVE QUERY chip in the schema tree marks outputs that behave this way.

For example, if this node sets a ticket's status to In progress and a later node sets it to Closed, an expression reading $vars.<nodeId>.output.Status after that point returns Closed, not the In progress value this node wrote.

Loop and data-transform collections cannot consume this output. The engine discards the write response, so unlike a Query entity records node there is no snapshot for them to fall back on.