← All Notion guides

Notion Guide

Notion Rollup Not Working? Fix Empty Results and Wrong Totals

← All Notion guides · Try the example

You have connected your databases, but the rollup is blank, shows a list instead of a total, or adds up the wrong amount. Start with one record and follow its connection. You usually do not need to rebuild the workspace.

Start here: Open the record with the wrong total. Check that its Relation contains the pages you want to include. Then check the rollup’s three choices: Relation → Property → Calculate. For a money total, use a numeric Amount property and Sum.

This guide uses a small, fictional client-and-invoice example. The setup follows Notion’s official Relations and Rollups documentation. It covers database settings, rather than API or integration errors.

1. Check the pages inside the relation

Creating a Relation property connects the databases. It does not automatically assign every invoice to the correct client. Open the client’s record and inspect its Invoices relation.

If the relation has no pages, choose the invoices that belong to that client. A client name typed into a Text or Select property is not a link to a client record.

When you created the relation from Invoices to Clients, you may have left it one-way. If you want a rollup in Clients, that database needs a relation containing the invoice pages. Enable the corresponding relation on Clients when appropriate; do not create a second independent connection just to make the same names appear.

2. Check which relation and property the rollup uses

A client might relate to both Projects and Invoices. A rollup using Projects cannot sum invoice amounts through the Invoices relation. Inspect the configuration rather than relying on its display name.

For total invoiced amount in Clients:

Relation: Invoices
Property: Amount
Calculate: Sum

Open one related invoice and check its Amount. If that property is empty, there is no amount there for the rollup to add. Fill in a known test amount in a practice copy and check the result.

3. If Sum is missing, check the source property type

For this example, Amount must be a Number property. You can format that number as a currency. Writing “$250” in a Text property does not turn it into a numeric amount.

Notion offers different calculations for different property types. If you selected a date or text property, look again at the selected source property before changing the whole database. Start with a plain Number property for your test, rather than debugging a complex formula at the same time.

4. If you see individual amounts, select Sum

Show original displays the selected values; Sum adds numeric values. A list such as 250, 400 and 150 is useful when checking the inputs, but it is not the total you asked for.

Count all is also a different calculation: it counts values instead of adding their amounts. Check Calculate after choosing the relation and property.

5. If the total is too small, check relation limits and missing links

A relation can be limited to 1 page or allow No limit. A client’s Invoices relation needs multiple pages if the client can have several invoices. A one-page limit makes that model unable to include them all.

The invoice’s Client relation can still have a one-page limit when each invoice belongs to one client. These are different directions: choose the limit that matches each job.

Compare the actual related invoice pages with the expected list. A missing link leaves an invoice out; a link to another client’s invoice adds the wrong amount.

6. A filtered view does not choose the rollup’s inputs

A dashboard might show only unpaid invoices. Hiding paid invoices in that view does not remove them from a client’s Invoices relation. A rollup using that relation and Amount still uses the connected records.

If your total should include only a subset, define that calculation deliberately. First confirm that the simple total is correct. Then build the unpaid-only calculation separately, rather than changing invoice links just to make the visible list match.

Try it: six invoices, two totals to check

Use two practice databases: Clients and Invoices. In Clients, create six fictional records: Acme Studio, Cedar Design, Northline, Fieldwork, Paper House and Orbit. In Invoices, add these six records. Amount is Number; Client is a Relation to Clients with the corresponding Invoices relation shown in Clients.

Fictional practice data — enter amounts as numbers
InvoiceClientAmount
INV-01Acme Studio250
INV-02Acme Studio400
INV-03Acme Studio150
INV-04Cedar Design600
INV-05Northline300
INV-06Fieldwork200

In Clients, create a Total invoiced Rollup: Invoices → Amount → Sum. Check the linked pages before comparing these expected results.

Acme Studio: 800 from INV-01, INV-02 and INV-03.
Cedar Design: 600 from INV-04.
Northline and Fieldwork should total 300 and 200 respectively. Paper House and Orbit have no invoices in this example.
Acme shows 650. What should I check?

Compare its linked pages and source amounts. In this example, 250 + 400 = 650, so start by checking whether INV-03 is linked to Acme and whether its Amount is 150. The number alone does not prove which setting is wrong.

How can I check that the connection responds?

In your practice copy, change INV-03 from 150 to 175. Acme’s expected total becomes 825. Restore 150 afterwards; the expected total returns to 800. This checks one input through one connection.

Visual example: trace the inputs before fixing the total
Related invoices

INV-01: 250
INV-02: 400
INV-03: 150

Rollup settings

Relation: Invoices
Property: Amount (Number)
Calculate: Sum

Acme Studio

Expected total: 800
Change INV-03 to 175 → 825
Restore 150 → 800

Illustrative calculation using the fictional invoice records above; not a Notion screenshot.

If the settings look right and it still will not calculate

Try the small Number-based example in a separate practice area. If that works, compare it with the failing record: selected data source, related pages, source property and calculation. If the simple example also fails, record those details and the symptom for Notion support. Avoid deleting working databases while trying to identify the cause.

Keep a short diagnostic record

Before changing settings, write down the expected related invoices, their numeric amounts and the expected total. For Acme’s practice data, that is INV-01, INV-02 and INV-03 with 250, 400 and 150: total 800.

Change one input at a time
ObservationCheckExpected after correction
Total 650Inspect the INV-03 relation and its 150 amount800 with all three intended amounts
Total 1400Check whether Cedar’s 600 invoice was also related800 when only Acme’s invoices contribute
INV-03 changed to 175Keep the same three related records825; restore 150 afterward

These are diagnostic starting points, not proof of the cause. Missing values, unexpected records and wrong property selection can produce similar symptoms. Record what you changed and whether the observed result matched the prediction.

Avoid replacing the rollup with a manually typed total. Keep the manual amount as an expected result for comparison while fixing the source connection.

Frequently asked questions

Why is my Notion rollup empty?

Start with the relation on the affected record. Check that it contains the intended pages, then inspect the selected relation, source property and calculation. A typed client name is not a relation link.

Why can I not select Sum?

For this invoice example, select Amount as a Number property. Text that looks like a currency amount is still text. Available calculations depend on the selected property type.

Why does my rollup show a list of amounts?

Check Calculate. Show original displays the individual values; Sum adds the numeric amounts.

Will filtering my invoice view change the client total?

No. Hiding invoices in a view does not remove them from the relation used by this rollup. Define any unpaid-only calculation separately after checking the simple total.

Should an empty invoice amount mean zero?

Do not assume that. Review missing amounts separately and enter zero only when it is an intentional value.

Build the database relation first, compare relations and rollups, and use a linked view to display the source elsewhere.