Feature Request: Support for Sub-Records or Nested Data within a Row

[Sohail2949000]

1. Problem Statement
Our team manages complex workflows in Teable where a single record often requires multiple related sub-items, notes, or internal tasks. Currently, Teable does not allow users to create structured sub-records within a row. To work around this limitation, we often use multiple linked tables or add lengthy text fields, both of which become difficult to organize, track, and scale.

2. Desired Solution
We request the ability to add sub-records directly within a row. This feature would allow users to create a nested structure where each main record can contain multiple related sub-items.

Key capabilities should include:

• A "Sub-Records" field type or an expandable section within a row where users can add, edit, and delete sub-items.
• Configurable fields for sub-records (e.g., task description, assignee, due date, status).
• Optional toggle to show/hide sub-records within table views, ensuring a clean interface.
• Ability to filter, sort, or search based on sub-record data.

3. Example Use Cases

• Project Management: A main row is a "Project," and sub-records are "Tasks" or "Milestones."
• Order Management: An "Order" row contains sub-records for each "Order Item" with details like SKU, quantity, and status.
• Client Files: A "Client" record includes sub-records for "Contacts," "Meetings," or "Communications."

4. Alternative Approaches Considered
We have tried using separate linked tables, but this requires additional setup and complicates the user experience. Embedding multi-line text or attachment fields lacks structure and is not easily filterable or actionable.

5. Impact & Benefits

• Enhanced Organization: Keeps related information contextually together without creating excessive tables.
• Improved Workflow: Enables detailed tracking within a single record, reducing navigation between tables.
• Scalable Structure: Makes it easier to manage hierarchical or multi-step processes directly within Teable.

We believe this feature would significantly improve how teams handle detailed, nested data and support more sophisticated use cases in Teable.

Thank you for your consideration.