Skip to main content

πŸ“˜ Next Plus Data Tables – Explained

Alex Merkin avatar
Written by Alex Merkin
Updated over 2 months ago

A clear guide to understanding the main database tables used in dashboards and reporting. This guide provides an overview of the key data tables in Next Plus, what they are for, how they connect, and when to use them.

πŸ”„ 1. workflowsessionitem – Workflow Session

Tracks actual production sessions. Includes start/end time, quantities, user ID, workflow connection, and status.

  • Key Fields: _id, userid, workflowid, workorderid, validquantity, start, progress

  • Joins: workflow, workorder, usermodel

  • Use It For: Production dashboards, performance KPIs, session analytics

πŸ§ͺ 2. sessioncustomfieldview – Session Field Values

Stores any custom input during a session: torque, barcode, temperatures, approvals.

  • Key Fields: fieldid, valuenumber, userid, workflowsessionitemid, nodeid

  • Joins: field, workflowsessionitem, usermodel

  • Use It For: QA tracking, inspection summaries, user performance

🏷 3. field – Custom Field Definitions

Metadata for all session/form fields, including title, type, and value ranges.

  • Key Fields: title, type, min, max

  • Joins: Used by sessioncustomfieldview

  • Use It For: Labeling and interpreting custom fields

πŸ“‹ 4. workorder – Work Orders

Contains all work order definitions: part, quantity, deadlines, and progress.

  • Key Fields: sku, quantity, statusname, workflowid, closed

  • Joins: workflow, workflowsessionitem

  • Use It For: Order tracking, backlog reports, ERP sync validation

πŸ‘€ 5. usermodel – Users

User profiles and attributes such as name, status, and group affiliation.

  • Key Fields: displayname, email, active, groups

  • Joins: userid in all activity tables

  • Use It For: Linking actions to people, user-based filters

πŸ“¦ 6. stock – Inventory & Produced Items

Shows units actually produced, with quantity and serials. Can be connected to sessions or orders.

  • Key Fields: sku, serial, quantity, validquantity, workorderid

  • Joins: workorder, workflowsessionitem

  • Use It For: Yield reports, quality tracking, inventory snapshots

πŸ”— 7. sessionstockview – Link: Session ↔ Stock

Maps each session to the stock items it worked on.

  • Key Fields: stockid, workflowsessionitemid

  • Joins: stock, workflowsessionitem

  • Use It For: Backtracking item lifecycle, multi-stock sessions

🧩 8. stockitemview – Stock Components

Breakdown of parts inside stock items (like kits or subassemblies).

  • Key Fields: stockid, sku, serial

  • Joins: stock

  • Use It For: BOM tracking, assembly validation

πŸ›‘ 9. workflowsessionitemrecord – Step Events

Logs every action (enter, leave, sign) taken within a session step.

  • Key Fields: nodeid, reason, userid, start, end

  • Joins: workflowsessionitem, usermodel

  • Use It For: Process flow analytics, bottleneck detection

🧠 Tips

  • Use usermodel to resolve IDs into names

  • Combine sessioncustomfieldview with field to get readable input types

  • Use workflowsessionitemrecord to analyze workflow step-level behaviors

  • Combine stock + sessionstockview + workflowsessionitem for full traceability

Did this answer your question?