8: How-to Guides
      Back to home
      1. Home
      2. 8: How-to Guides

      How to Import Data into Tables in Rayven.io (temp)

      Rayven.io makes it easy to import data into your Primary and Secondary Tables using a simple interface. You can upload spreadsheets (CSV/Excel), copy-paste rows, or connect to live data sources via integrations. This helps you populate tables quickly

      Use Cases

      • Upload an initial device list into a primary table.

      • Import sensor readings, logs, or notes into secondary tables.

      • Load data from another system (ERP, CMMS, SCADA, etc.) via CSV.

      • Batch update existing records with new values.

      How It Works

      Each table in Rayven has built-in import tools that:

      • Allow file upload via CSV/XLSX

      • Match column headers to table fields

      • Validate row data before saving

      • Optionally append or overwrite existing data

      You can also automate imports using integrations or workflows, but this article focuses on manual imports via the UI.

      Step-by-Step Instructions

      Step 1: Navigate to Your Table

      1. Go to Tables Configuration.

      2. Locate the table (Primary or Secondary).

      3. Click the View action icon to open it.

      Step 2: Click “Import”

      1. Click the Import or Upload Data button (usually top right).

      2. Select your file:

        • Format: CSV or Excel

        • Size: Within system limits (shown during upload)

      Step 3: Map Fields

      1. Rayven will attempt to auto-map columns based on headers.

      2. Review the mapping:

        • Match each column to the correct field in your table.

        • Skip any columns that aren’t needed.

      🧠 Tip: Column names in your file should match your table fields to speed up mapping.

      Step 4: Validate and Confirm

      1. Rayven will run a validation check:

        • Invalid formats, empty required fields, duplicates, etc.

      2. If all rows are valid, click Import to proceed.

      3. If there are errors, fix them directly in the interface or re-upload a corrected file.

      Step 5: Verify the Import

      1. Once uploaded, browse your table to confirm the rows appear correctly.

      2. Sort or filter fields to spot-check for accuracy.

      3. Optionally, tag or label this import (e.g., “April 2025 Initial Load”).

      Best Practices

      • Use unique identifiers (like Device ID) to ensure clean imports.

      • Clean your data before uploading (remove blanks, standardize formats).

      • Test with a small sample file first to avoid mass errors.

      • Keep an import log: Who uploaded what and when?

      • Don’t overwrite Primary Table data unless necessary — it's your source of truth.

      Examples

      Table Type Example Import File
      Primary (Devices) device_id, location, type, status
      Secondary (Logs) device_id, timestamp, event_type, notes
      Secondary (Operators) operator_id, name, assigned_device_id

      Troubleshooting

      • File won’t upload?
        Check format, size limits, or invalid characters in column names.

      • Fields not mapping correctly?
        Make sure headers in your file match the field names in your table.

      • Rows skipped during import?
        Hover over error icon to see what failed (e.g., date format, missing values).

      • Data appears but is incorrect?
        Verify field types (e.g., string vs. number) and adjust your import formatting.

      Next Steps

      👉 How to Configure Your Tables
      👉 How to Edit Table Data Manually
      👉 How to Link Imported Data in a Workflow
      👉 Automating Data Import with Integrations