When you apply a filter to a Notion database that contains a Relation column, the pages displayed in that Relation may appear in an unexpected order. This happens because the Relation column does not inherit the sorting rules of the parent view. Instead, it defaults to the order set in the original database or the last manual arrangement. This article explains why this order mismatch occurs, how to correct it, and what to do if the problem persists.
Key Takeaways: Fixing Relation Page Order in Filtered Views
- Relation column properties: A Relation shows pages in the order of the linked database, not the current filtered view.
- Sort rule in the linked database: Adding a sort rule to the linked database overrides the default page order for all Relation columns.
- Rollup column with formula: Creating a Rollup to display a sequential number from the linked database gives you a manual sort key.
Why a Relation Column Ignores Your Filtered View Sort
A Relation column in Notion links to another database. When you click a Relation cell, the popup shows pages from that linked database. The order of those pages is determined by the linked database’s default sort, not by the sort you set in the current view. If the linked database has no explicit sort rule, Notion displays pages in the order they were created. This is why a filtered view may show Relation pages in what seems like a random or wrong sequence.
The core issue is that a filter changes which rows appear in the current view but does not affect the Relation popup. The Relation popup is essentially a mini-view of the linked database. If the linked database has no sort, the popup defaults to creation order. If the linked database has a sort rule, the popup respects that rule. Therefore, to control the order in a Relation popup, you must set a sort rule in the linked database itself.
How Notion Handles Default Ordering
When a database is created, Notion assigns an internal creation timestamp. If no sort is applied, the database displays pages in that creation order. This applies to the main view and to any Relation popup that references that database. If you manually drag pages in a database view, that manual order becomes the default unless a sort rule is added. Manual order is stored per view, not per database. A Relation popup does not respect manual order from a specific view; it uses the database-wide default.
Steps to Correct the Order of Relation Pages in a Filtered View
Follow these steps to make the Relation column display pages in the order you want, even when the parent view is filtered.
- Open the linked database
Navigate to the database that the Relation column links to. This is the source of the pages shown in the Relation popup. - Add a sort rule to the linked database
Click the sort button at the top right of the database view. Add a sort rule based on a property such as Created Time, Last Edited Time, or a custom date column. Choose ascending or descending order. This sort rule will apply to every Relation popup that references this database. - Verify the sort applies to the Relation popup
Go back to the original database with the filtered view. Click any Relation cell. The popup should now list pages in the order defined by the sort rule you added in the linked database. - Create a Rollup column for a custom sort key (optional)
If the linked database does not have a suitable date property, add a Number column to the linked database. Enter a number for each page to define your custom order. Then, in the original database, create a Rollup column that pulls that number from the Relation. You can then sort the filtered view by this Rollup column. Note that this Rollup sort only affects the current view, not the Relation popup itself. - Use a formula to generate a sequence number (advanced)
In the linked database, add a Formula column with the formulaprop("Created Time").formatDate("YYYYMMDDHHmmss"). This generates a timestamp string that sorts chronologically. The Relation popup will display pages in this order if you set a sort rule based on this formula column.
If Relation Pages Still Appear in Wrong Order After Setting a Sort
Even after adding a sort rule to the linked database, you may encounter situations where the Relation popup still shows pages in an unexpected order. This section covers the most common reasons and their fixes.
Relation Popup Shows Creation Order Despite a Sort Rule
If the linked database has a sort rule but the Relation popup ignores it, the sort rule may be set on a view that is not the default view. Notion respects the sort rule of the first view in the linked database. Ensure that the view with your sort rule is the leftmost tab in the linked database. If the default view has no sort, the Relation popup will fall back to creation order. To fix this, drag the sorted view to the first position in the linked database’s tab bar.
Filtered View Sort and Relation Popup Sort Conflict
You may have a sort rule in the filtered view that sorts by a property not present in the linked database. This sort does not affect the Relation popup. The only way to align the two orders is to ensure the linked database’s sort rule matches the sort you want in the Relation popup. For example, if the filtered view sorts by Priority and the linked database has a Priority property, add a sort rule in the linked database by Priority as well.
Manual Drag Order in the Linked Database Overrides Sort
If someone manually dragged pages in the linked database view, that manual order may override the sort rule. Notion treats manual order as a special sort state. To force the sort rule to apply, remove any manual ordering by clicking the sort button and adding a rule. If the sort button shows “Sort: Manual,” click it and choose a property to sort by. This will replace the manual order with the rule-based sort.
| Item | Relation Popup Order | Filtered View Order |
|---|---|---|
| Default (no sort rule) | Creation order of linked database | Creation order of current database |
| Sort rule in linked database | Respects linked database sort rule | Unaffected by linked database sort |
| Sort rule in current view | Ignored | Respects current view sort rule |
| Manual drag in linked database | Respects manual order if no sort rule | Ignored |
You now understand why a Relation column can show pages in an unexpected order when the parent view is filtered. The fix is to set a sort rule in the linked database, which the Relation popup respects. For finer control, use a Rollup column to bring a sort key into the current view. As an advanced tip, consider using a Formula column in the linked database that generates a sortable timestamp string; this ensures the Relation popup always lists pages in the exact chronological order you need.