Why Notion Relation Cannot Be Used in Sub-Item Property Definition

You cannot select a Relation property when defining a sub-item property in a Notion database. This limitation appears when you try to link a sub-item property to a related database but the Relation option is missing or grayed out. The cause is a structural restriction in Notion’s database schema: sub-item properties only support simple property types such as Text, Number, Select, Date, and Checkbox. This article explains exactly why Relation properties are blocked in sub-item definitions and what you can do instead to achieve related data connections.

Why Notion Blocks Relation Properties in Sub-Item Definitions

Notion’s sub-item feature lets you nest rows inside a parent row to represent subtasks, line items, or child records. When you enable sub-items on a database, Notion creates a hidden self-referential relation between the parent row and its children. This hidden relation already uses the database’s own ID structure. Adding a second Relation property to a sub-item property definition would create a circular dependency or a cross-database link that the sub-item system cannot resolve. Notion engineers decided to restrict sub-item property types to avoid performance degradation and data inconsistency. The blocked types include Relation, Rollup, Formula, Created By, Created Time, Last Edited By, and Last Edited Time. Only static or single-value types like Text, Number, Select, Multi-Select, Date, Checkbox, Email, Phone, URL, and Status are allowed.

How Sub-Item Properties Work Under the Hood

When you toggle on sub-items in a database, Notion adds a hidden property called Parent item. This property is a Relation that points back to the same database. Each sub-item row stores the ID of its parent row in this hidden relation. The sub-item property definition you configure (e.g., “Sub-item Name” or “Sub-item Details”) is a template that applies only to child rows. Notion treats these template properties as extensions of the parent row’s schema but with a restricted set of allowed types. Because the hidden relation already consumes the database’s internal linking capacity, adding another Relation to the template would require Notion to manage two separate relation graphs for the same set of rows, which it does not support.

Steps to Confirm the Limitation and Find Workarounds

1. Open your database and enable sub-items
   Navigate to the database where you want sub-items. Click the three-dot menu in the top-right corner of the database view. Select Layout from the menu. In the Layout panel, toggle on Sub-items. Notion will add the hidden Parent item relation and a default sub-item property named after your database.
2. Try to add a Relation property to the sub-item template
   Click the + button in the property header row of the sub-item section. In the property type dropdown, scroll through the list. Notice that Relation does not appear. The available types stop at the simple categories. This confirms the restriction.
3. Use a linked database view on the parent row instead
   If you need to show related records from another database inside a sub-item context, create a linked database view on the parent row. Open the parent row page. Type /linked and select Linked database. Choose the target database and apply a filter that matches the parent row’s ID or a common property. This displays the related data without requiring a Relation on the sub-item property.
4. Add a Rollup property to the parent database
   If the sub-item needs to display a value from a related database, add a Rollup property to the parent database instead. Create a Relation property on the parent database linking to the target database. Then add a Rollup property that references that Relation and pulls the desired field. The Rollup value will appear in the parent row and can be seen in sub-item views.
5. Use a formula property with a relation lookup in the parent
   For advanced scenarios, add a Formula property to the parent database that references a Relation property. For example, prop("Related Project").name displays the name of the related record. This formula output can be shown in sub-item rows if you add a Formula property to the sub-item template, but the formula itself must be defined on the parent.

Common Misconceptions and Edge Cases

Relation Property Appears in the Full Database but Not in Sub-Item Template

Some users think they can add a Relation to the main database and then drag it into the sub-item section. This does not work. The sub-item template has its own property list separate from the main database. A Relation defined on the main database will not appear in the sub-item property editor. If you need the Relation value visible in sub-item rows, add a Formula property to the sub-item template that references the parent’s Relation via prop("Parent item").prop("Your Relation Name"). This formula will show the related data in each sub-item row.

Using a Rollup in the Sub-Item Template Is Also Blocked

Rollup properties are blocked for the same reason as Relation: they require a cross-database lookup. The sub-item template does not allow any computed or relation-based property type. You must place Rollups on the parent database and then reference them via a Formula in the sub-item template as described above.

Sub-Item Properties Inherit from Parent but Not from Other Databases

A sub-item row inherits all properties from its parent database, including Relation and Rollup properties defined at the parent level. However, those properties are not editable within the sub-item property definition. You can only view or edit them on the parent row. This inheritance pattern means you can still see related data in sub-item rows if the parent has the Relation, but you cannot add a new Relation exclusively for sub-items.

Notion Sub-Item Property Types: Allowed vs Blocked

Property Type	Allowed in Sub-Item Template	Workaround Available
Text	Yes	N/A
Number	Yes	N/A
Select	Yes	N/A
Multi-Select	Yes	N/A
Date	Yes	N/A
Checkbox	Yes	N/A
Email	Yes	N/A
Phone	Yes	N/A
URL	Yes	N/A
Status	Yes	N/A
Relation	No	Linked database view or parent-level Relation with Formula
Rollup	No	Parent-level Rollup with Formula
Formula	No	N/A (Formula not needed if parent has Formula)
Created By	No	N/A
Created Time	No	N/A
Last Edited By	No	N/A
Last Edited Time	No	N/A

You now understand why Notion blocks Relation properties in sub-item property definitions. The hidden self-referential relation and the need to avoid circular dependencies prevent cross-database links in sub-item templates. Use a linked database view on the parent row to display related records, or add a Formula property to the sub-item template that pulls data from a parent-level Relation. For a more structured approach, create a Rollup on the parent database and reference it with a Formula in the sub-item template. This keeps your data connected without violating Notion’s sub-item constraints.