The Tables Configuration Page in Rayven.io enables you to create, view, and manage both Primary and Secondary tables. These are essential components of your app’s data model, providing the structure that workflows, AI agents, and dashboards rely on.
Overview
-
Primary Tables: These are your core datasets — the single source of truth for key entities like devices, users, or assets.
-
Secondary Tables: These serve as relational extensions, useful for logging events, storing historical data, or attaching supplementary records to a primary entity.
Together, these tables support scalable, relational architectures that are easy to maintain and extend.
Use Cases
-
Centralize key records with a Devices table.
-
Track maintenance using a Maintenance Logs secondary table linked to devices.
-
Store high-frequency readings in a Sensor Readings table.
-
Organize staff assignments with an Operators table tied to sites or devices.
How It Works
The page is divided into two main sections:
Primary Tables
These contain foundational datasets with unique identifiers. Other tables and workflows reference these records.
Secondary Tables
These are linked datasets designed to support one-to-many or many-to-many relationships with the primary table. Examples include logs, readings, and user actions.
Step-by-Step Instructions
Step 1: Create a New Table
-
Click Add New in either the Primary or Secondary section.
-
Enter a Table Name.
-
Define your columns and data types.
-
Click Save to confirm.
💡 Tip: Primary tables should always include a unique ID field (e.g., device_id).
Step 2: View an Existing Table
-
Find the table in its respective section.
-
Click the View icon.
-
Explore the table’s rows, columns, and any linked records.
Step 3: Edit a Table
-
Click the Edit icon next to the table.
-
Perform actions such as:
-
Renaming columns
-
Adding/removing fields
-
Changing data types (use caution)
-
Adding new records manually or by import
-
Best Practices
-
Use clear, consistent naming conventions (e.g.,
DeviceStatus_Log,Sensor_Readings_2024). -
Keep Primary Tables lean — only store essential fields.
-
Use Secondary Tables for logs, time-series, and related context.
-
Avoid circular references between tables.
-
Periodically audit and clean up tables to maintain performance.
Table Examples
| Table Name | Table Type | Use Case |
|---|---|---|
| Devices | Primary Table | Master list of tracked devices |
| Maintenance Logs | Secondary Table | Daily logs linked to devices |
| Sensor Readings | Secondary Table | Time-series readings per device |
| Operators | Secondary Table | Personnel responsible per site or asset |
Troubleshooting
Can’t link tables?
Make sure your secondary table includes a reference column that matches a unique ID in the primary table.
Changes not saving?
Look for validation errors or required fields that are missing.
Table not appearing?
Try refreshing the page or verify user permissions.
Q&A
Q: Can I link multiple secondary tables to one primary table?
Yes. Each primary record can be referenced by multiple secondary tables, making it easy to track historical or contextual data.
Q: Can tables be used across workflows and dashboards?
Absolutely. Tables serve as both input and output sources for workflows and can be bound to widgets in interfaces.
Q: How can I import data into a table?
Use the import function available in the table actions menu to upload data in bulk via CSV.
Q: Can I restrict who can edit or view a table?
Yes. Access is controlled through user roles and group-level permissions within the workspace.
Next Steps
-
[How to Import Data into a Table]
-
[How to Link Primary and Secondary Tables in a Workflow]
-
[Best Practices for Table Schema Design]
-
[How to Use Table Data in Dashboards]