4.2 Using Labels Effectively
      Back to home
      1. Home
      2. 4: Data Tables & Labels
      3. 4.2 Using Labels Effectively

      Grouping Data Using Labels

      How to organise, filter, and control data access in Rayven using Labels.

      Overview

      Labels in Rayven are structured attributes used to categorise and filter Primary Table records. They enable you to organise data into meaningful groups, control which records users can access, and customise how widgets and workflows display or calculate information.

      Labels are only available in Primary Tables and can be configured as Default, Single Label, or Multi-Label, each offering different flexibility and performance trade-offs. Once configured, label values can be used across User Groups, Interfaces, and Workflows for granular control of data visibility and processing.

      Using Labels in Rayven

      Label Types

      • Default (No Labelling) – Stores values but does not support grouping. Most efficient for storage and performance.

      • Single Label – Groups records by a single attribute; cannot be combined with other labels for multi-level filtering.

      • Multi-Label – Allows combining multiple label columns for complex, multi-level filtering; most flexible but least efficient.

      Selecting Label Values for User Groups

      When creating a User Group, you can assign specific label values to control data visibility.

      • Example: If the label is Department and the value is Accounting, members of that User Group will only see Primary Table rows where Department = Accounting.

      • Supports AND/OR logic for combining multiple label values.

      • Default: Primary Label = All (users see all Primary Table rows unless filtered).

      Note: For many applications, using labels may be unnecessary. The default setting ensures the app functions without additional configuration.

      Controlling Widget Display Using Labels

      In Frontend Nodes, you can set how many widgets appear based on label settings:

      • One Widget per UID – Displays one widget for each Primary Table record.

      • One Widget per Label Value – Displays one widget for each unique value in the label column.

      • One Widget per Label – Displays one widget for the label itself, regardless of how many values it contains (default).

      When aggregating data for a label, you can configure how it’s calculated (e.g., sum, average, last value received).

      Performing Calculations Based on Labels

      Some workflow nodes (e.g., Data Summary) can calculate values grouped by:

      • UID – Individual Primary Table records.

      • Label Value – Groups of UIDs sharing the same label value.

      Triggering Workflows Using Labels

      Triggerable nodes (e.g., Trigger Node, many Connector Nodes) can execute logic:

      • For each UID in the Primary Table.

      • For each UID with a specific label value.

      • Or just once per defined interval (default).

      Best Practices for Grouping Data with Labels

      1. Keep it simple – Use the default Primary Label = All unless filtering is required.

      2. Plan label structure early – Decide if you need Single or Multi-Label to avoid future rework.

      3. Use meaningful names – Label columns should clearly indicate their grouping purpose (e.g., Region, Customer Type).

      4. Combine with User Groups – Labels become most powerful when paired with label-based User Group filters.

      5. Test with sample data – Validate that your label values produce the intended grouping before going live.

      Summary

      Labels are a core feature in Rayven for categorising and filtering Primary Table data. They provide a flexible way to control visibility for different user groups, adjust widget display logic, and run calculations or triggers on specific subsets of records. By planning label use carefully and leveraging them alongside User Groups and workflows, you can create highly tailored data experiences.

      FAQs

      Can I use labels in Secondary Tables?
      No. Labels are only available in Primary Tables. Secondary Tables can still be linked to Primary Table UIDs or labels but do not have label columns themselves.

      What’s the difference between a label and a label value?
      A label is the column in the Primary Table (e.g., Region). A label value is the specific entry in that column (e.g., Sydney).

      Do I have to use labels?
      No. The default Primary Label = All allows applications to function without grouping or filtering.

      Can I combine multiple labels to filter data?
      Yes. Use Multi-Label columns to create advanced filters with AND/OR logic.

      Do labels affect performance?
      Yes. Multi-Label is less efficient than Single Label or Default, so choose based on the level of flexibility you need.