When you set up a rollup property in a Notion database, you expect it to display data from related records. But the rollup often shows only one value even when the source database has multiple matching entries. This happens because a rollup property is designed to return a single aggregated result, such as a sum, average, or count, not a list of individual items. This article explains why the limitation exists and provides a concrete workaround using a linked database view to show all related values.
Key Takeaways: Notion Rollup Multiple Values Workaround
- Rollup > Show Original: Displays only the first related value instead of all values.
- Linked database view with a filter: Shows every related record in a separate block.
- Formula with join() and map(): Concatenates multiple values into a single text string.
Why a Rollup Property Cannot Show Multiple Values
A rollup property in Notion reads data from a related database through a relation property. When you configure the rollup, you must choose an aggregation function: Show Original, Show Unique, Count, Sum, Average, Min, Max, Median, Range, or Count Values. The Show Original option returns only the first value from the related records. Show Unique returns a comma-separated list of unique values, but it still collapses duplicates and does not preserve the full list order. The other functions produce a single number or text value. This behavior is by design — rollups are meant for aggregated calculations, not for listing all items.
If you need to see every related value individually, you must use a different approach. A rollup alone cannot output a multi-row or multi-value list in a single property cell. The workaround involves creating a linked database view that filters to show only records related to the current row. This gives you a live, scrollable list of all related items. For cases where you need the values inline, a formula property can combine them into a single text string.
Workaround: Use a Linked Database View to Show All Related Values
The most reliable workaround is to place a linked database view inside the current database page and filter it to show only records that match the current page. This method works for any number of related records and updates automatically when you add or remove relations. It requires a relation property between the two databases and a rollup property that can pull a unique identifier, but the rollup is only used for filtering, not for display.
- Create the relation property
Open the database that will contain the linked view. Add a relation property that connects to the target database. For example, if you want to show all tasks assigned to a project, create a relation from the project database to the task database. - Add a rollup property for the page title
In the same database, create a rollup property. Set the relation to the one you just created. Under Property, select the title or any unique text field from the target database. Under Calculate, choose Show Original. This rollup will later be used in a filter, but it will show only the first value. - Open the page where you want the list
Click on a page in the current database to open it. Type /linked view of database and select the target database. A linked view block appears. - Add a filter to the linked view
Click the linked view, then click Filter. Add a filter condition: Where the rollup property (from step 2) contains the current page’s title. If the target database has a unique ID or name, use that instead. This ensures only records related to the current page show up. - Adjust the view layout
Change the view to Table, Board, Gallery, or List as needed. The linked view now displays every related record. When you add a new relation, the view updates instantly.
Alternative: Use a Formula to Combine Multiple Values into Text
If you need the values to appear inline in a property cell (for example, in a database view or export), you can use a formula property. This approach works best when the number of related records is small and you do not need to interact with each item individually. The formula uses the map() and join() functions to collect values from the related database through the relation property.
- Create a relation property
Ensure a relation property exists between the current database and the target database. - Add a formula property
In the current database, add a new formula property. Name it something like “Related Values Text”. - Write the formula
Enter the following formula, replacing “Relation” with your relation property name and “Name” with the property you want to display from the related database:Relation.map(current.Name).join(", ")
This collects the Name property from every related record and joins them with a comma and space. - Check the result
The formula cell now shows all related values separated by commas. If a record has no relations, the cell displays an empty string.
If the Workaround Still Does Not Show All Values
Linked view filter returns no results
If the linked view shows zero records, the filter condition may be too strict. Verify that the rollup property contains the exact text of the current page’s title. If the title has extra spaces or characters, the filter fails. Use a simpler filter: instead of “contains the current page’s title,” try filtering by the relation property directly. Notion does not allow filtering a linked view by a relation property from the parent page, so you may need to add a text property to the target database that matches the current page’s name and filter on that.
Formula shows only one value when multiple exist
A formula using map() should show all values. If it shows only one, the relation property may not be pointing to multiple records. Check the relation setup: open the relation property on the source database and ensure it allows multiple records. If it is set to “Limit to one,” change it to “Allow multiple.” After changing, the formula will update automatically.
Rollup with Show Unique still missing some values
Show Unique removes duplicate values and may not show the order you expect. If you need all values including duplicates in the original order, use the formula method instead. The rollup Show Unique is not designed for complete lists; it is an aggregation function, not a display tool.
Rollup Aggregation vs Formula vs Linked View: Methods Compared
| Item | Rollup (Show Unique) | Formula with map() and join() | Linked Database View |
|---|---|---|---|
| Displays all values | No — removes duplicates and may truncate | Yes — includes duplicates in order | Yes — every related record as a row |
| Interactive (clickable) | No — text only | No — text only | Yes — each record opens its page |
| Updates automatically | Yes | Yes | Yes |
| Works in database view | Yes — shows in a cell | Yes — shows in a cell | No — shows only on the individual page |
| Best for | Quick count or unique list | Inline summary text | Full list with details |
The rollup property is designed for aggregated data, not for listing multiple values. When you need to see every related record, use a linked database view with a filter. For an inline text summary, use a formula with map() and join(). Both methods give you control over how related data appears in Notion. After setting up the workaround, test it by adding a new relation and confirming the linked view or formula updates. For complex databases, consider adding a template button that automatically inserts the linked view on new pages.