When you set up a linked database view in Notion, you expect it to remember the sort order you applied. But sometimes the view resets, showing items in the default creation order instead of your custom arrangement. This happens because the sort setting is tied to the specific view configuration, and a conflict between the source database and the linked view can cause the sort rule to drop. This article explains why the sort order breaks and provides a step-by-step fix to lock it in place.
Key Takeaways: Keeping Sort Order in a Linked Database View
- View menu > Sort > Add a sort: Applies a permanent sort rule to the current linked view only.
- Duplicate the linked view before editing: Prevents overwriting the original view configuration.
- Check the source database view: If the source view changes, the linked view can lose its sort order.
Why a Linked Database View Loses Its Sort Order
A linked database view is a copy of a view from the source database. When you create a linked view, Notion duplicates the view configuration, including any sort rules that were active at that moment. However, the linked view is not a static snapshot. It remains connected to the source database’s data but uses its own view settings. The problem occurs when the source database’s original view is later edited. If someone changes the sort order in the source view, the linked view may inherit that change instead of keeping its own custom sort. Another common cause is using the linked view inside a template or a synced block, where the view resets each time the template is duplicated. Finally, a bug in Notion’s view caching can cause the sort rule to disappear after a page reload.
Steps to Fix and Lock the Sort Order in a Linked View
Follow these steps to apply a sort rule that stays permanent. Each step assumes you have edit permissions for the page containing the linked view.
- Open the linked database view
Navigate to the page where the linked view is displayed. Click anywhere inside the view to select it. The view toolbar appears at the top of the database. - Create a new view for the linked database
Click the view name in the toolbar. At the bottom of the dropdown, click “Add a view.” Give the new view a distinct name, such as “Sorted View.” This creates a fresh view that is not connected to any pre-existing sort rule from the source database. - Apply the sort rule to the new view
With the new view selected, click the “Sort” button in the toolbar. Click “Add a sort.” Choose the property you want to sort by, such as “Date Created” or “Priority.” Set the order to ascending or descending. The sort rule is now attached to this specific view. - Rename and hide the old view
Click the view name again. Find the original linked view that was losing its sort order. Click the three-dot menu next to its name and select “Rename.” Change it to “Old View” so you can identify it later. Then click the three-dot menu again and choose “Hide” to remove it from the view tabs. The old view still exists but will not interfere with the new sorted view. - Test the sort order persistence
Add a new item to the source database. Return to the page with your linked view. The new item should appear in the correct sorted position. Reload the page. The sort order should remain unchanged.
If Notion Still Has Issues After the Main Fix
Linked view inside a template resets on duplication
When you create a page from a template that contains a linked database view, the view may reset to the default sort order. This happens because the template duplicates the view configuration, but the sort rule is not always copied correctly. To fix this, open the newly created page and repeat the steps above: add a new view, apply the sort, and hide the old view. After saving, the template will retain the sort order for future duplicates.
Sort order changes when another collaborator edits the source
If a teammate changes the sort order in the source database’s view, your linked view might change too. This occurs when your linked view is using the same view name as the source. To prevent this, always give your linked view a unique name that does not match any view in the source database. The linked view will then keep its own independent sort configuration.
Sort rule disappears after page reload
A caching bug in Notion can cause the sort rule to vanish after a hard reload. To work around this, open the linked view’s sort menu and remove the existing sort. Click “Add a sort” and reapply the same rule. Then click “Save” in the view toolbar. This forces Notion to write the sort rule to the database. If the problem persists, clear your browser cache or try a different browser.
Linked Database View vs Source Database View: Sort Behavior Compared
| Item | Linked Database View | Source Database View |
|---|---|---|
| Sort rule location | Stored in the linked view configuration | Stored in the source database view configuration |
| Editable by viewers | Only if they have edit access to the page | Only if they have edit access to the source database |
| Affected by source changes | Only if the view name matches the source view name | Directly affected by any edit |
| Reset on template use | Frequently resets | Not applicable |
| Number of views supported | Unlimited, each with independent sort rules | Unlimited |
You can now lock the sort order in any linked database view by creating a dedicated view and applying the sort rule. Next time you set up a linked view, duplicate the view first and name it something unique to avoid conflicts with the source. For advanced setups, use the “Group” feature alongside sort to organize items by category and then sort within each group. This combination gives you full control over how data appears without unexpected resets.