# Update entity record

> Configure the Update entity record node to change a Data Fabric record, and read its output in later nodes.

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](/data-service/automation-cloud/latest/user-guide/entities-in-vs-code): how to define an entity in a VS Code solution.

## Configuration

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

| Option | Description |
|---|---|
| **Entity name** | Select the **Data Fabric entity** directly, set a **Filter** (field, operator, value) to identify the record, and select the **Fields to update**. |
| **Entity reference** | Reuse a record already located by a [Query entity records](node-query-entity-records.md) node earlier in the workflow, instead of re-specifying the entity and filter. |

### Entity name

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

![Update entity record node's Properties panel set to Entity name, showing a Data Fabric entity picker, a Filter row, and a Fields to update checklist.](https://dev-assets.cms.uipath.com/assets/images/maestro/node-update-entity-record-properties-3d8682b0.webp)

### Entity reference

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.

![Update entity record node's Properties panel set to Entity reference, prompting to select a Query entity records node from the workflow.](https://dev-assets.cms.uipath.com/assets/images/maestro/node-update-entity-record-reference-mode-f23a789a.webp)

This node doesn't support the **Error handling** tab.

## Output

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>`.

### Live reference behavior

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.

## Next steps

- [Data Fabric entity nodes](data-fabric-entity-nodes.md): the other entity record nodes.
- [Node reference](node-reference.md): every node and how to configure it.
- [Community](community.md): ask questions and share workflows with other builders on the UiPath Forum.