Application Configuration Interfaces
      Back to home
      1. Home
      2. 2: Platform Overview
      3. Application Configuration Interfaces

      Tables - Manage Primary & Secondary Tables

      The Tables Configuration Page in Rayven.io allows you to create, view, and manage both Primary and Secondary tables. These tables are used to structure your data model, define relationships, and organize datasets in a scalable and efficient way.

      • Primary Tables serve as your central source of truth.

      • Secondary Tables act as extensions or enrichments of primary data.

      This page is key to building structured, relational data models that power workflows, AI agents, and dashboards in Rayven.


      Use Cases

      • Create a centralized Devices table with unique records.

      • Link additional data (e.g., status updates, maintenance logs) via secondary tables.

      • Update schema, edit records, or track table changes over time.

      • Maintain clean, well-organized datasets to optimize performance.


      How It Works

      The page is divided into two sections:

      Primary Table

      Displays the main dataset containing unique IDs and core records. This is the foundational table that other data links to.

      Secondary Tables

      Lists supporting datasets that connect to the primary table. These are useful for one-to-many or many-to-many relationships.


      Step-by-Step Instructions

      Step 1: Create a New Table

      1. Click Add New under the section you want (Primary or Secondary).

      2. Enter a Table Name.

      3. Define the columns (fields) and data types.

      4. Save the configuration.

       Tip: Primary tables should have a unique identifier field (e.g., Device ID).

      Step 2: View an Existing Table

      1. Under either section, locate the table you want.

      2. Click the View action icon.

      3. Inspect rows, columns, and linked relationships.

      Step 3: Edit a Table

      1. Use the Edit action icon next to the table.

      2. You can:

        • Rename columns

        • Add or remove fields

        • Change data types (with caution)

        • Add new rows of data manually or via import

      Best Practices

      • Use consistent naming conventions for clarity (e.g., DeviceStatus_Log, Sensor_Readings_2024).

      • Keep primary tables lean — only essential data.

      • Use secondary tables to track logs, historical data, or related attributes.

      • Avoid circular dependencies between tables.

      • Audit your tables regularly to remove outdated or unused entries.

      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

      Troubleshooting

      • Can’t link tables?
        Ensure your secondary table has a reference field that matches a unique ID in the primary table.

      • Changes not saving?
        Check for validation errors in the column configuration or empty required fields.

      • Table not appearing?
        Refresh the page or check for permission/access restrictions.

      Next Steps

      👉 How to Import Data into a Table
      👉 How to Link Secondary Tables in a Workflow
      👉 Best Practices for Table Schema Design
      👉 How to Clean and Normalize Data in Rayven.io