- Introduction
- Getting started
- Build on any canvas
- Build with Case
- Reference
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Build with Flow
- Build with BPMN
- Operating
- Monitoring
- Optimizing
- Reference information
Create entity record
Create entity record node for writing a new record to a Data Fabric entity from a workflow, without a connection.
Creates a new 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.
Configuration
| Field | Required | Description |
|---|---|---|
| Data Fabric entity | Yes | The entity to create a record in. Select Refresh schema if the entity's fields changed since you added the node. |
| Field values | Yes | Select + Select fields to choose which fields to set, then provide a value for each selected field. At least one field value is required. |
This node doesn't support the Error handling tab.
Output
The node's output mirrors all of the entity's fields. The fields and types vary by entity and typically include the entity's standard system fields (such as Id, CreateTime, and CreatedBy) alongside your custom fields. Access them downstream as $vars.<nodeId>.output.<fieldName>.
Live reference behavior
The output is a live reference to the created 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 creates a ticket with status Open and a later node sets that ticket to Closed, an expression reading $vars.<nodeId>.output.Status after that point returns Closed, not the Open value this node wrote.
Loop and data-transform collections are the exception. They read a snapshot of the record taken when the node ran.
Next steps
- Data Fabric entity nodes: the other entity record nodes.
- Node reference: every node and how to configure it.