What is the join limit?
The "join limit" refers to a limitation on the number of tables and fields that can be efficiently queried when TrackVia assembles a table's records. Behind the scenes, certain field types and design elements each require the database to "join" additional data sources together, and there is a ceiling on how many joins a single table can use.
TrackVia has a hard limit of 61 joins per table. Two joins are in use by default on every table — the built-in Created By and Last Updated By user fields — leaving 59 joins available for your design.
What counts toward the join limit?
The following count as one join each:
- Drop Down fields
- Image fields
- Document fields
- Attachments fields (one join per field, no matter how many files are uploaded)
- Application User fields
- Application Group fields
- Relationships (each parent or child relationship the table participates in)
- Calculated or Triggered fields that reference a single field from any of the field types above
Calculated and Triggered fields can count as more than one join:
- A Calculated or Triggered field that references one of the above field types on a parent or child table counts as two joins (one for the relationship traversal, one for the referenced field).
- If calculations reference other calculations, the join count can increase exponentially — each layer of nesting multiplies the joins required. Deeply chained calculated fields are the most common way tables hit the limit unexpectedly.
Field types that do not consume joins include Single Line, Paragraph, Number, Percentage, Currency, Auto Counter, Email, Link, Date, Date and Time, and Checkbox fields, along with Calculated/Triggered fields that only reference these non-join field types on the same table.
Estimating a Table's Join Usage
To roughly estimate where a table stands, count:
- 2 (Created By + Last Updated By, always present)
- +1 for each Drop Down, Image, Document, Attachments, Application User, and Application Group field
- +1 for each relationship in the Table Relationships editor
- +1 for each Calculated/Triggered field referencing a join-type field on the same table
- +2 for each Calculated/Triggered field referencing a join-type field on a parent or child table
- Add extra for calculations that reference other calculations — trace each chain
If the total approaches 61, it's time to redesign.
What happens when you've reached the Join Limit?
If a table has reached the join limit, the clearest indicator is that the table's default view will be unable to load its data and will display an error.
Strategies to Stay Under the Join Limit
Split large tables. If a single table is accumulating dozens of relationships and drop downs, it's usually doing several jobs. Split it into multiple related tables, each with a focused purpose.
Flatten calculation chains. Because calculations that reference other calculations compound join usage, restructure deeply nested formulas to reference source fields directly where possible.
Consolidate file fields with Attachments. One Attachments field (one join, up to 25 files) can replace several separate Image and Document fields.
Audit drop downs. Every Drop Down field costs a join. For simple two-option choices, a Checkbox field (which does not consume a join) may work instead.
Remove unused relationships and fields. Audit the Table Relationships editor and the Table Builder periodically. (Be careful: deleting a relationship severs existing record links, and deleting a field destroys its data — see How to Create Table Relationships and How to Customize Tables.)
Design before you build. Sketch your table structure and estimate join usage per table before creating anything. See [Table Design Best Practices].
Related Videos
- Understanding "The Join Limit" — a 3-minute TrackVia University video on this topic.
Comments
0 comments
Please sign in to leave a comment.