4: Data Tables
      Back to home
      1. Home
      2. 4: Data Tables

      Table Data Format Types in Rayven.io

      Rayven.io offers a variety of data field types that can be used when configuring tables. These data types ensure that the structure and integrity of your records are maintained and that each field stores the correct kind of data for your application

      data-formats

      Rayven.io provides a variety of field types that can be configured when setting up MySQL tables. Choosing the correct field type ensures that your data remains accurate, structured, and efficient for use across workflows, dashboards, and integrations.

      This article explains each available data type, when to use it, and how it supports structured, scalable solutions.

      Basic Data Types

      Int

      Stores whole numbers (e.g., 10, -5, 42).
      Use Cases: Inventory quantities, status counters, IDs, index values.

      Decimal

      Stores floating-point numbers with precision (e.g., 10.5, -0.75).
      Use Cases: Temperatures, prices, percentages, or scientific readings.

      String

      Stores text values (alphanumeric or plain text).
      Use Cases: Names, descriptions, tags, email addresses.

      Date and Time Types

      Date

      Stores date-only values (e.g., 2025-06-15).
      Use Cases: Deadlines, scheduled events, birthdates, historical logs.

      Time

      Stores time-of-day values (e.g., 08:15, 17:30).
      Use Cases: Shift start/end times, scheduled triggers, recurring events.

      Choice-Based Fields

      Multi Choice

      Allows selection of one or more predefined values.
      Use Cases:

      • Status tags (e.g., Active, Inactive)

      • Roles or categories (e.g., Admin, Editor, Viewer)

      • Filterable labels

      Supports dropdowns or checkbox group UI elements.

      Special & Integration Fields

      Workflow Node

      Links the field to a specific node in a workflow.
      Use Cases:

      • Tracking the source of data

      • Auditing which logic path created a record

      • Binding metadata to automation events

      JSON Field

      Stores flexible, nested data in JSON format.
      Use Cases:

      • API responses

      • Sensor data payloads

      • Unstructured or semi-structured key-value pairs

      Choose this type for custom or dynamic data that doesn’t fit a strict schema.

      Reference Fields

      Reference Field

      Links to a record in another table, similar to a foreign key in relational databases.
      Use Cases:

      • Linking Customer_ID to the Customers table

      • Associating a record with a location, product, or category

      • Enabling real-time lookups and relational filtering in interfaces

      Reference fields help normalize datasets and avoid duplication.

      Summary Table

      Field Type Description Example Use Case
      Int Whole number Inventory count
      Decimal Precise floating-point number Temperature, price
      String Freeform text Name, label, description
      Date Calendar date only Deadline, birthday
      Time Time of day Shift start time
      Multi Choice Selectable fixed options Device status, user roles
      Workflow Node Tracks the origin node in a workflow Audit trail, trigger logging
      JSON Field Custom structure or nested data API payload, device metadata
      Reference Field Points to a related record in another table Link to customer, product, site
       

      Tips for Field Configuration

      • Choose the simplest field type that satisfies your data needs.

      • Use Reference Fields to normalize data and create scalable relationships.

      • Use JSON Fields only when dealing with variable or non-tabular content.

      • Keep Multi Choice options clear, concise, and regularly maintained.

      • Test field configurations with example records before committing to production use.

      Q&A

      Q: Which field type should I use for numeric values like prices or temperatures?

      A: Use the Decimal field type for any value requiring precision, such as currency, measurements, or sensor data.

      Q: When should I use a Reference Field instead of just a text field with an ID?

      A: Use a Reference Field when you want to link a record to another table and benefit from lookup functionality, relational filtering, and data consistency.

      Q: What is the purpose of a Workflow Node field?

      A: This field tracks which workflow node created or modified a record. It’s useful for auditing, debugging, or linking logic to table entries.

      Q: Can I store dynamic or complex values in a table field?

      A: Yes, use the JSON Field type to store structured but flexible data, such as payloads or variable metadata.

      Q: Is it possible to store multiple labels or tags in one field?

      A: Yes, use a Multi Choice field to allow selection of one or more predefined values, useful for categories, filters, or status tags.

      Q: What happens if I select the wrong field type?

      A: You can usually update the field type from the table editor, but be cautious—changing types can affect existing data. Always test changes on a copy of the table when possible.