When you toggle sub-items in a Notion database, you may notice that the column order of properties reverts to the default arrangement. This issue disrupts workflows that rely on a specific property order, such as priority columns or custom fields. The problem occurs because Notion treats sub-item toggles as a full view refresh, which can override your saved column layout. This article explains why the property order resets and provides steps to lock your preferred arrangement.
Key Takeaways: Preventing Property Order Resets in Notion Databases
- View Layout > Save As > Save current view as a new view: Creates a dedicated view that preserves your column order against toggle resets.
- Database > Layout > Lock view: Prevents accidental reordering and stabilizes property order during sub-item interactions.
- Database > Layout > Freeze columns: Keeps selected columns visible on the left side, reducing the impact of order resets.
Why Notion Database Property Order Resets When You Toggle Sub-Items
Notion databases rely on a view-based system where each view stores its own column order, filter, and sort settings. When you toggle a sub-item (expand or collapse a row with nested items), Notion refreshes the current view. This refresh can cause the property order to revert to the default arrangement defined by the view template or the database schema if the view was not explicitly saved after the last reorder. The issue is not a bug but a side effect of how Notion handles view states during dynamic interactions like sub-item toggles.
The root cause lies in the difference between a saved view and an unsaved view. If you reorder columns in a view that was created from a template or inherited from a parent database, the changes remain in memory until you explicitly save them. Sub-item toggles trigger a view reset that clears these unsaved modifications, returning the property order to the last saved state. This behavior is consistent across all database types, including table, board, and gallery views.
How View Templates Affect Property Order
When you create a new database from a template, the template defines a default property order. Any changes you make to this order are temporary unless you save the view as a new view or update the existing view. Toggling sub-items will revert to the template order because the view state is not persisted. This is especially common when using linked databases or databases synced from Notion’s template gallery.
The Role of Sub-Item Data Structure
Sub-items in Notion are not separate database entries but rather rows that belong to a parent row. When you expand a parent row to view its sub-items, Notion re-renders the view to include the nested data. This re-rendering process can flush the current column order if the view was not saved. The same behavior occurs when collapsing sub-items, as the view recalculates its layout.
Steps to Lock Property Order and Prevent Resets
- Open the database view
Navigate to the Notion database where the property order resets. Ensure you are in the view that shows the sub-items. - Arrange properties to your preferred order
Drag and drop column headers to reorder the properties. Confirm the order matches what you want to keep. - Save the view as a new view
Click the view name dropdown at the top of the database. Select Save As. Enter a name for the new view, such as “Custom Order View.” This creates a dedicated view that stores your property order permanently. - Set the new view as default
In the view dropdown, click … > Set as default view. This ensures the view loads with your saved order every time. - Lock the view layout
Click the … menu in the view bar and select Lock view. This prevents accidental drag-and-drop changes that could trigger a reset. - Test sub-item toggles
Expand and collapse a few sub-items. Verify that the property order remains unchanged. If it resets, repeat steps 2 through 5 and ensure the view is saved before locking.
If you have multiple views that exhibit this behavior, repeat the process for each view. Locking a view only affects that specific view, not the entire database.
If Notion Still Resets Property Order After Saving the View
Property Order Resets in a Linked Database
Linked databases inherit the property order from the source database. To fix this, open the source database and save a new view with the desired order. Then, in the linked database, use the view dropdown to switch to that saved view. Toggling sub-items in the linked database should now preserve the order.
Property Order Resets After Adding New Properties
When you add new properties to a database, Notion appends them to the end of the column order. This can cause a visual reset if the view was saved before the new properties existed. To avoid this, after adding new properties, reorder them and save the view again. Locking the view will not prevent new properties from appearing, but it will keep the rest of the order stable.
Property Order Resets When Using API or Integrations
Third-party integrations that modify database properties can trigger view refreshes. If you use tools like Zapier or Make, ensure they do not alter property order. If the issue persists, pause the integration and test sub-item toggles. If the order holds, adjust the integration to avoid property reordering.
Notion Database View Features: Saved vs Unsaved vs Locked
| Feature | Saved View | Unsaved View | Locked View |
|---|---|---|---|
| Description | View stored with a custom name and settings | View used without explicit save | View with layout modifications disabled |
| Property order persistence | Persists after sub-item toggles | Resets to default on sub-item toggle | Persists and prevents drag reorder |
| How to create | View dropdown > Save As | Default view from template | View dropdown > Lock view |
| Best use case | Custom workflows with specific column order | Quick data entry without customization | Team databases where layout must stay fixed |
Understanding these three states helps you choose the right approach for your database. For most users, saving a view and then locking it provides the most reliable protection against property order resets.
You can now prevent property order resets by saving and locking dedicated views in your Notion databases. The key action is to use the Save As option before toggling sub-items. For additional stability, enable Lock view from the view dropdown. As an advanced tip, create a master view with all properties in your preferred order, then use the Duplicate view feature to create variants for different teams while keeping the base order intact.