In Rayven.io, Primary and Secondary Tables are essential for organizing and relating your data. This article explains how to create new fields (columns) and add records (rows) to both types of tables — helping you structure your data model, maintain

Use Cases
-
Add new fields like
Asset Type
,City
, orStatus
to your Primary Table -
Insert new records into your Secondary Table (e.g., maintenance entries or operator logs)
-
Enforce data rules such as uniqueness, required values, and visibility settings
-
Create linked records that enhance reporting and workflow logic
How It Works
Each table has a Manage View where you can:
-
Search for and filter existing data
-
Add or edit fields (columns)
-
Add or edit records (rows)
-
Configure validation rules and UI visibility
You’ll find these options under:
🛠️ Actions → Manage Your Primary/Secondary Table
Step-by-Step Instructions
🧱 1. Manage Your Table
-
Navigate to the Tables Configuration page.
-
Locate your Primary or Secondary Table.
-
Click Actions → Manage Your Table to open it.
-
Use the Search bar to filter and inspect existing rows.
➕ 2. Add a New Column (Field)
To Add a New Column:
-
Click Add New Column under the Actions menu.
-
Complete the form with the following:
Field | Description |
---|---|
Data Type* | Select field type: String , Number , Date , etc. |
Label Type | Choose display behavior: Display Only (read-only field) |
Column Name* | This is the user-facing name, e.g., Asset Type , City Name |
Link to Interface | Optionally connect this field to an external UI component |
Hide Column in User Interface | Check to make the column invisible in dashboards |
Required Value in All Fields | Enforce mandatory entry for all rows |
Unique Values in All Fields | Prevent duplicate values (ideal for UID , Serial No. , etc.) |
-
Click Save to add the column to your table.
➕ 3. Add a New Row (Record)
To Add a New Row:
-
Click Add New Row under the Actions menu.
-
Fill out the required fields in the row creation form:
Field | Description |
---|---|
UID* | A unique identifier (e.g., device_001 , user_ABC ) |
UID Display Name | A readable name (e.g., “Main Plant Chiller”, “John Doe”) |
Additional Fields | Any custom fields you’ve defined (e.g., Asset Type , Status , etc.) |
-
Click Save to insert the new record into the table.
🔄 You can add multiple rows one by one, or use the Import function for bulk additions.
Best Practices
-
Use clear, consistent column names (e.g.,
Asset_ID
,Install_Date
) -
Always define a unique UID for Primary Tables — it’s used in relationships
-
Use the “Required” and “Unique” options to prevent data issues later
-
Hide sensitive or internal-use fields using “Hide Column in UI”
-
Use linked Secondary Tables for logs, transactions, or historical data
Examples
Table Type | Example Column | Example Row |
---|---|---|
Primary | Asset Type (String) |
UID: device_001 , Asset Type: Chiller |
Secondary | Maintenance Date (Date) |
UID: log_123 , Linked Asset: device_001 , Status: Passed |
Troubleshooting
-
Can’t add column?
Check that the column name isn’t already in use or conflicting with reserved names. -
Duplicate UID error?
Make sure yourUID
is globally unique across the table. -
Field not showing in dashboards?
Check if “Hide in UI” is enabled. -
Missing required field warning?
Ensure all mandatory fields have values before saving.
Next Steps
👉 How to Link Primary and Secondary Tables in a Workflow
👉 How to Import Data into Tables
👉 How to Use Table Data in Dashboards
👉 How to Enforce Data Validation Rules