Record

This node represents a single database record (model) and provides access to its properties.

The Record node (DbModel2) fetches, monitors, and exposes data from a specific database table row.

The Record node is the primary way to work with individual data items from your backend. It connects to a specific collection (table) and retrieves a record by its ID. It automatically exposes output ports for every column in the table schema and updates in real-time when the data changes.

Inputs

General

Data	Description
Class	The database collection (table) this record belongs to (e.g., "Users", "Products").
Id Source	"Specify explicitly" (default) or "From repeater". If "From repeater", it automatically grabs the ID from a parent list context.
Id	The unique ID of the record to fetch. Only visible if Id Source is "Specify explicitly".

Actions

Signal	Description
Fetch	Manually triggers a data fetch from the server. If not connected, the node fetches automatically when the ID is set.

Outputs

General

Data	Description
Id	The ID of the currently loaded record.

Properties

Data	Description
*	Dynamic outputs for every column in your database table (e.g., "Name", "Email", "Price").

Changed Events

Signal	Description
* Changed	Dynamic signals for every column (e.g., "Name Changed"). Triggered specifically when that property updates.

Events

Signal	Description
Fetched	Triggered when data is successfully loaded from the server.
Changed	Triggered when any property on the record changes.
Failure	Triggered if the record cannot be found or loaded.

Error

Data	Description
Error	Error message if the fetch failed.

Usage

Displaying Data

1. Select the Class (e.g., "Product").
2. Connect a Product ID to the Id input.
3. The node will expand to show outputs like "Name", "Description", "Price".
4. Connect these outputs to Text or Image nodes to display the data.

Real-Time Updates

The Record node subscribes to changes. If another user (or another part of your app) updates this record, the outputs will update automatically, and the Changed signal will fire.

Using in a List

Inside a Repeater:

1. Set Id Source to "From repeater".
2. The node will automatically find the correct record for each row in the list.

Detailed Behavior

• Schema Discovery: The node communicates with the backend to discover the table schema and generate ports.
• Caching: Data is cached in the global model scope. Multiple Record nodes pointing to the same ID share the same underlying data model.
• Supabase Integration: Automatically discovers tables from Supabase if configured.

Troubleshooting

• Outputs Missing: If your database schema changed, try refreshing the page or re-selecting the Class to regenerate ports.
• No Data: Ensure the Id is correct and that you have permission (RLS policies) to view this record.