Tables and Fields
Tables are the foundation of your Lotics workspace. Each table defines a schema with typed fields, stores records (rows of data), and supports multiple views: filtered, sorted, and grouped perspectives on the same underlying data. Everything updates in real time across all connected users.
Table Structure
A Lotics workspace contains tables, and each table has three layers: fields define the schema (what data can be stored), records hold the actual data (one row per entity), and views provide different perspectives on that data (which records to show, in what order, grouped how). This separation means you define your data model once and create as many views as your team needs.
Fields are typed and validated. When you add a Number field, only numeric values are accepted. When you add a Single Select field, values must come from the defined option list. This type safety prevents data quality issues at the source. No more free-text fields where some people type "$1,000" and others type "1000 USD".
Tables can hold tens of thousands of records and remain performant. The query engine supports server-side filtering, sorting, and pagination, so views load quickly even on large datasets. Real-time updates via WebSocket ensure every team member sees the latest data without refreshing.
Field Types
Lotics supports 13 field types that cover the full range of operational data. Each type has specific configuration options and validation rules. The table below lists every available type with its variants and typical use cases.
Choosing the right field type matters for downstream features. A Number field enables rollup aggregations (sum, average). A Record Link field enables lookups and rollups across tables. A Date field enables timeline views and deadline-based workflow triggers. The type system is not just about validation. It determines what you can compute and automate.
| Field Type | Variants / Options | Use Cases |
|---|---|---|
| Text | Plain text, URL/link, Rich text (formatted content) | Names, descriptions, notes, URLs, formatted documentation |
| Number | Number, Currency (with currency code), Percentage | Quantities, prices, margins, completion rates, financial figures |
| Date | Date only, Date and time (with timezone support) | Deadlines, ship dates, created/updated timestamps, scheduling |
| Boolean | True/false checkbox | Approval flags, completion status, active/inactive toggles |
| Single Select | One option from a defined list, color-coded | Status (Draft/Active/Closed), priority (Low/Medium/High), category |
| Multi Select | Multiple options from a defined list, color-coded | Tags, skills, applicable regions, product categories |
| Member | Assign one or more workspace members | Owner, assignee, reviewer, responsible team member |
| Record Link | Link to records in another table, bidirectional | Shipment to customer, invoice to order, task to project |
| Lookup | Read-only, pulls values from linked records | Show customer name on shipment, display order total on invoice line |
| Rollup | Aggregate linked records: sum, average, min, max, count | Total order value, number of shipments, average delivery time |
| Formula | Computed values using expression engine | Profit margin (revenue - cost), days until deadline, conditional labels |
| File | Documents, images, PDFs. Multiple files per cell | Contracts, photos, invoices, certificates, signed documents |
| Button | Trigger a workflow on click | Generate invoice, send notification, approve request, start process |
Computed Fields
Three field types (Lookup, Rollup, and Formula) are computed automatically from other data. They are read-only: you never enter values manually. Instead, they derive their values from linked records, aggregations, or expressions, and they update in real time when the source data changes.
Lookup fields pull values from records linked via a Record Link field. If your Shipments table links to a Customers table, a lookup field on Shipments can display the customer's email, phone number, or any other field, without duplicating data. When the customer record is updated, every shipment that links to it reflects the change immediately.
Rollup fields aggregate values across linked records. If an Orders table links to an Order Lines table, a rollup on Orders can compute the total order value (sum of line amounts), the number of line items (count), or the most expensive item (max). Supported aggregation functions are sum, average, min, max, and count. Formula fields use an expression engine to compute values from other fields in the same record: arithmetic, string manipulation, date calculations, and conditional logic.
Record Linking
Record Link fields connect data across tables, forming a relational graph within your workspace. A shipment record links to a customer record, which links to invoice records, which link to payment records. These connections are bidirectional. When you link Shipment A to Customer B, Customer B automatically shows Shipment A in its linked records.
Linked records are the foundation for Lookup and Rollup fields. Without links, these computed fields have nothing to traverse. A well-designed link structure lets you pull any piece of data from anywhere in your workspace without duplication. Need the customer's region on a shipment? Link shipments to customers, then add a lookup field.
Links also enable cross-table workflow logic. A workflow triggered by a shipment status change can read the linked customer record to find the email address, then read linked invoice records to attach a PDF. The relational structure you build with Record Link fields determines what your workflows and AI assistant can access and act on.
Views
Each table supports multiple views, and each view has its own independent configuration: which records to show (filters), what order to display them (sorts), which fields are visible and in what order (field visibility), how to group rows (grouping), and how to color-code rows or cells (color rules). All views share the same underlying data. Changes in one view appear in all others.
Views are how different team members see the same data in the way that matters to them. The operations manager sees all shipments sorted by deadline with overdue items highlighted. The sales team sees only their assigned deals grouped by stage. The finance team sees invoices filtered by payment status. Everyone works from the same source of truth.
All views update in real time via WebSocket. When a team member updates a record, every other user with a view open sees the change instantly. No refresh needed. This applies to record data, filter results, sort order, and grouping. Real-time collaboration is not an add-on feature; it is built into every layer of the view system.
Real-Time Collaboration
Multiple team members can edit the same table simultaneously. Changes propagate to all connected clients within milliseconds via WebSocket. There is no save button. Edits are persisted and broadcast as they happen. This includes record value changes, record creation and deletion, field schema changes, and view configuration updates.
The real-time system is designed for operational teams where data changes frequently and decisions depend on current state. When a warehouse team marks a shipment as dispatched, the operations dashboard updates immediately. When a salesperson closes a deal, the revenue rollup on the team summary table reflects it without delay.
Computed fields (lookups, rollups, formulas) cascade in real time. When a source record changes, every computed field that depends on it recalculates and pushes the new value to all connected clients. This cascade follows the dependency graph. A change to an order line item updates the order total rollup, which updates the customer lifetime value formula, which updates the customer segment classification.