You added a linked database view to a page expecting a formula column to calculate values from a source database in a different workspace, but the formula field shows an error or remains blank. This happens because Notion formulas are strictly scoped to the database they belong to, and linked views do not change that scope. This article explains the technical limitation, shows how to verify the issue, and provides workarounds to achieve cross-workspace calculations.
Key Takeaways: Notion Formula Scoping in Linked Views
- Formula scope is database-local: A formula property only reads data from rows inside its own database, not from the original source database of a linked view.
- Linked View is a filter, not a data bridge: A linked view displays a filtered copy of the source database, but formulas in the linked view can only operate on properties that exist in the linked database.
- Cross-workspace calculation requires manual syncing or third-party tools: To aggregate data from another workspace, you must export, duplicate, or use an integration like Zapier or Make.
Why Notion Formulas Are Scoped to a Single Database
Notion formulas are designed to compute values using properties from the same database row. When you add a formula property to a database, it can reference other properties in that same database, but it cannot reach across to a different database, let alone a different workspace. This is a core architectural choice: formulas are evaluated within the context of the database they are defined in, using only the data stored in that database’s rows.
A linked database view does not create a new database. It creates a view that references the source database’s data. If that source database is in another workspace, the linked view in your current workspace cannot run formulas that depend on the source database’s properties. The formula property in the linked view is a property of the linked database (the destination), not the source. Therefore, the formula has no access to the source database’s rows or their properties.
In technical terms, Notion’s formula engine executes in the context of the database ID that contains the formula property. A linked view displays rows from a different database ID, but any formula you add to the linked view’s database cannot read the source database’s property values because those values belong to a different database ID. This is not a bug; it is a deliberate limitation to maintain data isolation and performance across workspaces.
Steps to Confirm the Scope Limitation in a Linked View
Follow these steps to verify that the formula cannot access source data from another workspace.
- Locate the linked database view
On your page, find the linked database view that pulls data from a database in a different workspace. Click the view name to select it. - Open the linked database properties
Click the three-dot icon in the upper-right corner of the view and select Properties. Note that the properties listed belong to the linked database, not the source database. You cannot add a formula that references a source property that is not visible in this list. - Add a test formula property
Click Add a Property and choose Formula. Enter a simple formula likeprop("Name") + " test". If the Name property exists in the linked database, the formula works. If you try to reference a property that only exists in the source database, the formula will show an error or return an empty result. - Observe the error behavior
If the formula references a missing property, Notion displays a red error message: “No property named X” or the formula cell remains blank. This confirms that the formula cannot see source properties. - Check the source database directly
Open the source database in its own workspace. Verify that the property you want to compute exists there. Then return to the linked view and note that the formula still fails because the two databases are separate.
If Notion Still Has Issues After the Main Fix
Formula shows error even when referencing a property that exists in the linked view
If the formula references a property that is actually present in the linked database but still shows an error, the property name might be misspelled or the property type is incompatible. For example, a formula that tries to add text to a number property will fail. Check the property name in the Properties menu and ensure the formula uses the exact spelling and capitalization. Also verify that the data types match the formula function requirements. For instance, the contains() function expects text, not a number.
Linked view shows stale data and formulas do not update
A linked view may cache data from the source database, especially if the source is in a different workspace. If the source database updates but the linked view does not reflect the change, refresh the page or close and reopen the linked view. If the formula still does not update, check that the source database’s properties have not been renamed or deleted. Notion does not automatically sync formula results across workspace boundaries; you must trigger a manual refresh by reloading the page.
Formula works in the source database but not in the linked view
This is expected behavior. The formula in the source database can access all properties of that database. When you create a linked view in a different workspace, the linked database is a separate entity. The formula you add to the linked view cannot see the source database’s properties. To compute the same value in the linked view, you must recreate the formula using only properties that exist in the linked database. If the linked database does not contain the necessary properties, you cannot compute the value via formula.
Notion Formula Scope: Source Database vs Linked View vs Duplicated Database
| Item | Source Database | Linked View (Same Workspace) | Linked View (Different Workspace) |
|---|---|---|---|
| Formula can reference its own properties | Yes | Yes | Yes |
| Formula can reference source database properties | N/A | No | No |
| Formula can use rollup from another database | Yes, if both databases are in the same workspace | No, rollup requires direct relation | No |
| Data updates automatically | Yes | Yes, with cache delay | Yes, with cache delay |
| Can add new formula properties | Yes | Yes, but scoped to linked database | Yes, but scoped to linked database |
To compute values from a source database in another workspace, you must either duplicate the database into the current workspace or use an automation tool like Zapier to copy specific property values into the destination database. Manual duplication gives you full formula access but breaks live syncing. Automation tools can keep data in sync but require a paid subscription and setup time.
You now understand why Notion formulas cannot compute across workspaces in a linked view: the formula engine is database-local and cannot read properties from a database in another workspace. To work around this, duplicate the source database into the current workspace or use a third-party integration to sync property values. For simple calculations, consider exporting the data to a spreadsheet and importing it back into the destination database. As an advanced tip, use Notion’s API to fetch source data and update the destination database programmatically for real-time cross-workspace calculations.