You need a way to track which assets depend on other assets in your Notion workspace. A Relation property connects two databases, allowing you to link a server to its underlying hardware or a software license to the computer it runs on. This article explains how to create a Relation between an asset database and a dependency database, populate it with linked records, and use Rollup properties to surface critical details like status or purchase dates.
Key Takeaways: Notion Relation for Asset Dependency Tracking
- Relation property in the asset database: Links each asset record to one or more dependency records in a second database.
- Rollup property on the dependency database: Displays a summary field from the linked asset, such as status or location.
- Linked View of the dependency database: Shows all related dependencies inside the asset page for quick scanning.
What a Relation Does for Asset Dependency Tracking
A Notion Relation creates a two-way link between two databases. In asset dependency tracking, you have a primary asset database that holds records like servers, workstations, or network switches. A second database contains dependency records such as power supplies, software licenses, or network cables. The Relation connects each asset to its dependencies. When you add a Relation to the asset database, each asset page shows a field where you can select one or more dependency records. The dependency database automatically gains a reciprocal Relation that lists the assets that depend on it.
Before you build the Relation, you need two existing databases. The first database should contain the assets you track. The second database should contain the dependency items. Both databases must have at least a Title property. No other properties are required, but you should add properties like Status, Location, or Purchase Date to make the Rollup useful later.
The Relation property does not store data on its own. It only stores references to records in the other database. This means you cannot filter or sort directly on a Relation column. To display summary information from the linked record, you add a Rollup property that pulls a specific field from the linked dependency.
Steps to Create a Relation Between Asset and Dependency Databases
Follow these steps to link your asset database to a dependency database. The steps assume you already have both databases open in your workspace.
- Open the asset database
Navigate to the page that contains your asset database. Click the database name at the top of the view to enter the database settings. - Add a Relation property
Click the + button in the top-right corner of the database view. Select Relation from the property type list. A dialog box appears asking you to choose the second database. - Select the dependency database
In the dialog, start typing the name of your dependency database. Click it when it appears. Notion creates the Relation property and automatically adds a reciprocal Relation to the dependency database. - Name the Relation property
After the Relation is created, the property name defaults to the name of the dependency database. Rename it to something descriptive like Dependencies or Linked Assets. Press Enter to save. - Open an asset record
Click any asset page to open it. Scroll to the Dependencies property field. Click inside the field to see a list of all records in the dependency database. - Link dependency records
Click one or more dependency records to link them to the asset. Each selected record appears as a blue pill inside the field. You can remove a link by clicking the X on the pill. - Verify the reciprocal link
Open a dependency record in the dependency database. Scroll to the reciprocal Relation property that Notion created. You should see the asset record listed there. This confirms the two-way link is working.
Adding a Rollup to Display Dependency Details
A Rollup property extracts a value from the linked dependency record and displays it inside the asset database. For example, you can show the Status of each linked dependency without opening the dependency page.
- Add a Rollup property
In the asset database, click the + button and select Rollup from the property type list. - Configure the Rollup
In the dialog, set the Relation field to the Dependencies property you just created. Set the Property field to the field you want to pull from the dependency database, for example Status. Set the Calculate field to Show original to display the raw value. - Name and save
Give the Rollup a name like Dependency Status. Click Create. The Rollup column now shows the Status value for each linked dependency.
Building a Linked View Inside the Asset Page
A linked database view inside the asset page shows all related dependencies in a table or board format. This helps you see the full dependency list at a glance.
- Open the asset page
Click any asset record to open its full page view. - Type /linked
On a blank line inside the page, type /linked and press Enter. A dialog appears asking you to select a database. - Select the dependency database
Choose the dependency database from the list. A new linked view appears showing all records in that database. - Filter the linked view
Click the Filter button above the linked view. Add a filter: Where the reciprocal Relation contains this page. This limits the view to only dependencies linked to the current asset. - Customize the view
Change the view type to Table, Board, or Gallery. Add or remove columns to show only the information you need, such as Name, Status, and Location.
Common Mistakes When Building Asset Dependency Relations
Relation shows no options to select
If the Relation field is empty and clicking it shows no records, the dependency database might be empty or the Relation property might point to the wrong database. Open the asset database settings, click the Dependencies property, and verify the linked database name. If it is correct, add at least one record to the dependency database.
Rollup shows an error or no value
A Rollup property returns an error when the linked dependency record does not have a value in the selected property. Open a dependency record and check that the property you chose in the Rollup configuration has data. If the property is empty, fill it in. The Rollup updates automatically.
Reciprocal Relation does not appear
Notion automatically creates a reciprocal Relation when you add a Relation. If you deleted it accidentally, you can re-create it. Open the dependency database settings, add a new Relation property, and select the asset database. This creates a second two-way link. Delete the original Relation from the asset database to avoid duplicate links.
Linked view shows all dependencies instead of only linked ones
The linked view defaults to showing every record in the dependency database. Apply a filter to restrict the view. Click Filter, then add Where the reciprocal Relation contains this page. Replace reciprocal Relation with the actual name of the Relation property in the dependency database.
Asset Database vs Dependency Database: Key Differences
| Item | Asset Database | Dependency Database |
|---|---|---|
| Primary purpose | Tracks the main items you manage, such as servers or workstations | Tracks components or resources that assets rely on, such as power supplies or licenses |
| Relation direction | Contains the Relation that links to dependencies | Contains the reciprocal Relation that lists which assets depend on it |
| Typical properties | Name, Status, Location, Assigned To, Purchase Date | Name, Type, Vendor, Expiration Date, Quantity |
| Rollup usage | Rollup pulls summary info from linked dependencies, like Status or Vendor | Rollup pulls summary info from linked assets, like Location or Assigned To |
| View style | Often uses a Table with a linked view of dependencies inside each page | Often uses a Board grouped by Type or Status |
You now have a working Notion Relation that links each asset to its dependencies. Use the Rollup property to surface key fields like Status or Location without opening dependency pages. For a more advanced setup, add a second Relation to track parent-child relationships between assets, such as a server being a child of a rack. This gives you a complete dependency map in one workspace.