When you try to add a sub-item to a task or project in Notion, you may see the error message Sub-Item Cannot Be Created and the action is blocked. This usually happens because the database view you are using has a sort rule applied that is incompatible with the hierarchical structure of sub-items. Notion requires sub-items to be placed directly under their parent row, but a locked sort order can prevent that placement. This article explains why the sort-locked view causes this error and provides the exact steps to fix it so you can add sub-items again.
Key Takeaways: Fixing Sub-Item Creation in a Sorted View
- Database view sort rule conflict: A sort rule forces rows into a fixed order, preventing Notion from placing a sub-item under its parent row.
- View > Sort > Remove sort: Removing the sort rule from the current view allows sub-items to be created normally.
- Create a filtered view without sort: Duplicate the view and remove the sort to keep your data organized while enabling sub-item creation.
Why a Sort-Locked View Blocks Sub-Item Creation
Notion databases allow you to sort rows by any property such as date, status, or priority. When you apply a sort, Notion locks the row order so that it follows the sort rule at all times. Sub-items in Notion are rows that belong to a parent row and must appear directly below that parent row in the database. If a sort rule is active, Notion cannot guarantee that a sub-item will stay directly under its parent because the sort would reposition it elsewhere. To prevent data inconsistency, Notion blocks sub-item creation when a sort is applied to the current view.
This behavior is by design. Notion treats sub-items as a form of row grouping that relies on manual or hierarchical ordering. A sort rule overrides that manual order, so the two features are incompatible in the same view. The error message appears only in the view with the sort rule. Other views in the same database that do not have a sort rule will allow sub-item creation without issue.
Steps to Remove the Sort Rule and Enable Sub-Items
To resolve the error, you must remove or modify the sort rule in the current database view. Follow these steps exactly.
- Open the database view that shows the error
Navigate to the Notion page containing the database. Make sure you are on the view where the Sub-Item Cannot Be Created message appears. Look at the view tabs at the top of the database. - Click the view name to open the view menu
Click the name of the current view, such as Table or Board. A dropdown menu appears with options for that view. - Select Sort from the view menu
In the dropdown, click Sort. A side panel opens showing all sort rules applied to this view. - Remove the sort rule
Click the X icon next to each sort rule to delete it. If you have multiple sort rules, remove all of them. Once no sort rules remain, the side panel shows No sorts applied. - Try adding a sub-item again
Click the parent row where you want to add a sub-item. Use the + icon on the row or press Ctrl+Shift+Enter on Windows or Cmd+Shift+Enter on Mac. The sub-item should now be created without the error.
If you need the sort rule for other purposes, consider duplicating the view and removing the sort from one copy. See the next section for that method.
If You Still Need the Sorted View: Create a Duplicate View Without Sort
You may want to keep the original sorted view for reporting or quick scanning. In that case, create a second view of the same database that has no sort rule. Use that view when adding sub-items.
- Click the Add a View button
At the top of the database, click the + icon to the right of the existing view tabs. A dialog appears. - Name the new view
Type a name such as Sub-Item View or Unsorted. Choose the same view type as your original view, for example Table. - Remove the sort rule from the new view
Click the new view tab. Follow steps 2 through 4 from the previous section to remove all sort rules from this view only. - Add sub-items in the new view
Switch to the new view whenever you need to create sub-items. The original view remains sorted as before.
Common Issues After Removing the Sort Rule
Sub-Item Still Cannot Be Created After Removing Sort
If the error persists after removing all sort rules, check if the view has a filter that hides the parent row. Sub-items cannot be added to a row that is not visible. Open the view menu, click Filter, and review the filter conditions. Remove any filter that may be hiding the parent row. Also check if the parent row is inside a collapsed group. Expand all groups by clicking the triangle icon next to the group header.
Sort Rule Returns After Refreshing the Page
If you removed the sort rule but it reappears after a page refresh, you may have edited a view that is shared or locked by a workspace owner. Check if the view is locked by looking for a lock icon next to the view name. If it is locked, you cannot modify the sort rule. Create a new view as described in the duplicate view method above. The new view will not be locked and you can remove the sort rule permanently.
Sub-Items Created but Disappear After Sorting Another View
Sub-items you created in the unsorted view remain attached to their parent row. If you switch back to the sorted view, the sub-items may be hidden because the sort rule places them at a different position in the list. To see them in the sorted view, remove the sort rule temporarily or add a filter that shows all items including sub-items. Sub-items are not deleted; they are just not displayed in the sorted view due to the sort order.
| Item | Sorted View (with sort rule) | Unsorted View (no sort rule) |
|---|---|---|
| Sub-item creation | Blocked with error message | Allowed |
| Row order | Controlled by sort rule | Manual or by creation order |
| Best use case | Reporting and quick scanning | Adding and managing sub-items |
| Filter compatibility | Works with filters | Works with filters |
Now you can create sub-items in your Notion database without the error message. Use the duplicate view method to preserve your sorted view for data analysis. For advanced workflows, consider using a relation property and rollup instead of sub-items if you need both sorting and hierarchical grouping in the same view.