--- title: "Link table records" slug: "link-table-records" tags: ["Tables", "Table Editor"] updated: 2025-11-14T18:47:26Z published: 2025-11-14T18:47:26Z canonical: "support.tulip.co/link-table-records" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Link table records *Establish relationships between table records with linked records* **In this guide, you will learn** - **What Linked Table Records are** - **Caution on Performance of Linked Records** - **How to link Table Records** ## Overview Tulip Tables are used to manage a wide variety of data including Work Orders, Skills matrix, Bill of Materials and many more. There will likely be a definable relationship between two tables (ex: assembly and sub-assembly data, shift schedule and operator information data). Linked Records, you can define, manage and visualize these relationships between different tables. ### Use cases **1. Display reference data (from a secondary table) in an interactive table** - Allows master data information to be displayed while not needing to duplicate columns - Should be used for key information only ![Reference data with linked records](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Reference%20data%20with%20linked%20records.png) **2. Create genealogy records / data** - Filtering views for genealogy data is easier with linked record - Recommendation to still store parent ID as a column for queries/aggregations (see limitations) **3. Easy ability for interactive table filtering using “is in” filter** ![Linked record interactive table filters](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Linked%20record%20interactive%20table%20filters.png) ## Caution on performance of Linked Records Low performance of linked records observed at scale While linked records provide the ability to relate tables to one another, Tulip has seen significant performance issues when this feature is used at large scale (i.e. several linked record columns in a Table, several hundred thousand records in a table). ### Limitations It's important to note that linked records have certain limitations with the following Tulip features: **Performance** - Many linked record columns in a table may result in performance issues - Can be more complex to manage due to inability to do import and required format for API **App Triggers** - Cannot load record directly for 1:1 relationships - All linked record fields are string arrays even if a 1:1 relationship - No error message if record is already linked **Import/Export** - Cannot import linked records via CSV import - CSV export leads to each linked record field becoming a string array **Table queries and aggregations** - No aggregation possible on linked fields - No filtering possible on linked field **Analytics** - Analytics can only refer to one table at a time. You cannot use linked records to analyze data from multiple tables at once. **UX limitations** After a linked record relationship has been created, only way to see the relationship type (one to one, one to many, etc.) is from within the “record card view” (UI within Tables page when clicking on a Table Record or editing a Table column name). ## Alternative approaches to linked records Here are recommended architecture designs for cases where you do not want to use linked records. #### One to One relationships or One to Many relationships You can “link” tables by storing the ID as a record in the table. **Example** In a Defects Table, rather than linking defects to a Work Orders table, create a ‘work order ID’ column in the Defects table and store one or more values in each row as a comma delineated list #### Many to Many Relationships You can store a string array to a table field containing the link of the information **Example** Rather than linking a set of Part Numbers that need a set of feature checks for quality, store an array of ids for checks required in each part record **Steps** 1. Create an array in app logic for needed links 2. Convert the array to string and store it in a table field 3. Convert the string back to an array if you need to use the data in filters, app logic for any subsequent logic, or linking. ## Link table records To link two table records together, you must add a **new** column, to establish and define the relationship. It's important to note that you can **not** link existing columns in a Tulip Table. Table Records are linked through the record's **ID**. When you add a linked record column to a table, you will be prompted to define the relationship between the two tables. Upon creation, a new column in the linked table will also be automatically created, leaving you with one column in each of your linked tables. These columns will be populated with the ID of each table record. To add link a table record, add a new column in one of the tables you wish to link, and select **Field Type: Linked Record**. A modal will pop-up with the following options: ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Linking%20Table%20Records_264410302.png) - **Label**: Define the column label within the Table you are currently working in - **Link to > Table**: Select table you'd like to link your record to - **Link to > Field Labe**l: Define the label of the column that will be populated in your linked table - **Link Type**: Define the type of relationship between the table records. If you're unsure of what relationship type is best suited for your data, check out this [article](https://database.guide/the-3-types-of-relationships-in-database-design/). NOTE Once you save the column, the link type can not be edited. ## Example In the following example, there are two Tables: - Assembly table - Parts table. Each assembly is made of multiple parts. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Linking%20Table%20Records_264408450.png) ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Linking%20Table%20Records_264408632.png) In the Assembly Table, we'll add a new column to establish the relationship between the two tables. Here the relationship type is *Many To Many*. This is because multiple parts can be used in multiple different assemblies, and vice versa. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Linking%20Table%20Records_264422766.png) After saving the column, the following columns are generated in each table: ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Linking%20Table%20Records_264424204.png) At this point, only the structure of the relationship has been defined between the tables. Now, it's time to point each table record to its specific linked record. To do this, click on a table record. The following modal will pop-up: ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Linking%20Table%20Records_264425121.png) Within the search bar, you will be able to select the ID(s) of the table record(s) you wish to link. As mentioned above, the relationship between linked table records are defined by the ID(s) of the table record(s). Below you can see what the tables look like after linking each Table Record: ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Linking%20Table%20Records_321463538.png) ## Further reading - [How To Manage Your Inventory Using Tables](https://support.tulip.co/docs/how-to-manage-your-inventory-using-tables) - [How To Modify Tables Within the App Editor](https://support.tulip.co/docs/how-to-modify-tables-within-the-app-editor) --- Did you find what you were looking for? You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question! **Tulip Tables** **Tulip Tables**are a global location to store your production data. Tables are made up of Records (rows). A single can be accessed from multiple apps or stations at the same time. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Tulip%20Tables%20Overview%20-%20Feature%20Overview.gif) **Linked Records** **Linked Records**are interconnections between multiple **Tulip Tables.**Fields in one Table can be mapped to another table. Linked records simplify traceability, genealogy, and data association for more advanced Tulip apps and app suites. **Table Record** A **Table Record** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from with an App Trigger. To edit a record it must be loaded into a **Table Record Placeholder.** **Tulip Tables** **Tulip Tables** are a global location to store your production data. **Tables** are made up of **Records** (rows). A single can be accessed from multiple apps or stations at the same time. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Tulip%20Tables%20Overview%20-%20Feature%20Overview(1).gif)