If you try to rename a Relation property in a Notion database, the edit box appears but the name does not save. This happens because Notion treats the Relation property name as a shared identifier between the two linked databases. Changing the name in one database can break the link, so the system blocks the edit. This article explains why the rename fails and provides a safe workaround to change the Relation property name without losing the connection.
Key Takeaways: Renaming a Notion Relation Property
- The Relation property name is shared: Both linked databases use the same property name. Changing it in one breaks the link.
- Notion blocks the rename to prevent data loss: The interface disables the save button or reverts the name to protect the connection.
- Create a new Relation and delete the old one: This workaround lets you use any name you want while preserving all existing data.
Why Notion Blocks Renaming a Relation Property
A Notion Relation property creates a two-way link between two databases. Each database has its own column with the same property name. The name acts as a key that tells Notion which databases are connected. When you edit the property name in one database, Notion cannot automatically update the name in the other database without risking a mismatch. If the names fall out of sync, the Relation stops working and existing links become orphaned.
Notion prevents this by making the property name read-only after the Relation is created. You can change the name in the property settings panel, but the change does not stick. The interface either shows a message that the name cannot be changed or silently reverts to the original name after you click away.
The Shared Name Constraint
When you create a Relation, you select a second database. Notion adds a property to both databases with the same name. That name is stored as a metadata link between the two databases. If you rename the property in Database A, Database B still has the old name. Notion does not propagate the rename. The result is a broken Relation with no easy way to repair it.
Why the Workaround Is Necessary
Because Notion does not allow a direct rename, the only safe method is to create a new Relation property with the desired name, copy the existing links, and then delete the old Relation. This process preserves all data and avoids any downtime in your workflow.
Workaround Steps to Rename a Relation Property
Follow these steps to rename a Relation property without losing the connection between your databases. The workaround uses a temporary Relation property and a formula to transfer the existing links.
- Open both linked databases
Navigate to the database that contains the Relation property you want to rename. Open the second database that is linked to it. Keep both tabs open in your browser or Notion app. - Create a new Relation property with the desired name
In the first database, click the plus sign next to the last column header. Select Relation from the property type list. In the dialog that appears, choose the same second database that the original Relation uses. Give the new Relation the name you want. Notion will create a matching property in the second database. - Add a Formula property to copy existing links
In the first database, create a Formula property. In the formula editor, type the name of the old Relation property exactly as it appears. For example, if the old Relation is named “Projects”, typeprop("Projects"). This formula outputs the linked pages from the old Relation. The formula will display the same linked pages as the old Relation. - Manually link each row to the new Relation
Click into the new Relation property cell for each row. Start typing the name of a page that is already linked in the old Relation. Notion will suggest the page. Select it to create the link. Repeat for every row that has a link in the old Relation. If you have many rows, consider using a temporary database view filtered by the old Relation to process rows in batches. - Delete the Formula property and the old Relation property
After all links are transferred, remove the Formula property by clicking its column header and selecting Delete. Then click the header of the old Relation property and choose Delete. Confirm the deletion. The new Relation property now holds all the links with the name you want. - Rename the new Relation property if needed
If you want the new Relation to have a slightly different name, you can rename it now. Because it is a brand new Relation, Notion allows the rename. Click the column header, select Edit property, and change the name. The change will apply to both linked databases.
If Notion Still Blocks the Workaround
The new Relation does not appear in the second database
Notion may not show the new Relation property in the second database immediately. Refresh the page or close and reopen the second database tab. If the property still does not appear, check that you selected the correct second database when creating the new Relation. Delete the new Relation and create it again, making sure to pick the exact same database as the original Relation.
Formula does not output the linked pages
The formula prop("OldRelationName") must match the old Relation property name exactly. Check for extra spaces or typos. If the old Relation name contains special characters, enclose it in quotes. For example, prop("Project Links"). The formula will output the linked pages as a list. If it shows an error, delete the formula property and create it again with the correct name.
Links do not transfer because the new Relation shows no suggestions
The new Relation may not suggest pages from the second database if the Relation was not created correctly. Delete the new Relation property from both databases. Refresh the first database page. Create the Relation again, ensuring you select the same second database and the same linking property type. After recreating, the suggestions should appear.
Original Relation vs New Relation: Key Differences
| Item | Original Relation | New Relation (Workaround) |
|---|---|---|
| Name change allowed | No | Yes, after creation |
| Existing links preserved | Yes, until deletion | Yes, after manual transfer |
| Time to set up | Instant | Depends on number of rows |
| Risk of broken links | None | Low if steps are followed exactly |
The workaround is the only way to change a Relation property name in Notion. It requires manual effort but guarantees data integrity. Use a filtered view to speed up the link transfer for databases with more than 50 rows.
You can now rename any Relation property in Notion by creating a new Relation and transferring the links. Try using a Rollup property with the new Relation to pull additional data from the linked database. After the transfer, you can also add a filter to the new Relation to show only specific linked pages, which the original Relation did not support.