You see the error “Rollup cannot be configured” when you try to set up a rollup property in a Notion database. This error occurs because the rollup property you selected points to a source property whose data type is incompatible with the rollup’s aggregation function. For example, you cannot sum text values or count dates. This article explains the exact cause of this property type conflict and provides step-by-step fixes to resolve it.
Key Takeaways: Fixing Rollup Property Type Conflicts in Notion
- Property type mismatch: The rollup’s aggregation function (sum, average, count, etc.) must match the source property’s data type, or the error appears.
- Change the source property type: Convert the related database property to a compatible type such as Number or Date before configuring the rollup.
- Use a formula as intermediary: Create a formula property in the related database that converts incompatible data into a number, then roll up that formula.
Why the “Rollup Cannot Be Configured” Error Appears
A rollup property in Notion pulls data from a related database and applies an aggregation. The rollup’s aggregation function must match the data type of the source property. If you choose Sum or Average, the source property must be a Number type. If you choose Count All or Count Values, the source must support counting — typically any property works, but Count Values requires a non-empty value. If you choose Earliest Date or Latest Date, the source must be a Date type. When you select an incompatible source property type, Notion disables the rollup and shows the error.
The error is not a bug. It is a deliberate restriction to prevent meaningless aggregation results. For instance, summing text values or averaging checkbox values produces no useful data. Notion blocks the configuration to enforce data integrity.
Steps to Fix the Rollup Property Type Conflict
Follow these steps in order. Each method resolves the conflict in a different way.
- Identify the incompatible source property
Open the database that contains the rollup property. Click the rollup property header and look at the “Rollup Configuration” panel. Note the related database and the source property selected. The source property name appears under “Property.” Write down its data type (Text, Number, Date, Select, etc.). - Change the source property type to match the aggregation
Navigate to the related database. Find the source property. Click the property header and choose “Edit property.” In the “Type” dropdown, select a type that matches your rollup aggregation. For Sum or Average, choose Number. For Earliest Date or Latest Date, choose Date. For Count Values, any type works but ensure the property contains values. After changing the type, go back to the original database. The rollup should now be configurable. - Create a formula property to convert incompatible data
If you cannot change the source property type because it breaks other relationships, create a formula property in the related database. Click the related database’s “+” button and select “Formula.” Name it “Rollup Helper.” Enter a formula that converts the source data into a number. For example, if the source is a Select property named “Status” with options “Done” and “Pending,” use:if(prop("Status") == "Done", 1, 0). This returns 1 for Done and 0 for Pending. Set the formula property type to Number. Then go back to the original database, edit the rollup, and choose this formula property as the source. - Use a different aggregation function
If changing the source property type is not possible and you cannot create a formula, change the rollup’s aggregation function. Click the rollup property header and open “Rollup Configuration.” Under “Calculate,” select a function compatible with the existing source property type. For example, if the source is a Text property, choose Count All — it counts all related rows regardless of the text value. If the source is a Date property, choose Earliest Date or Latest Date. This avoids the type conflict entirely. - Delete and recreate the rollup property
If the rollup remains unconfigurable after trying the above steps, delete the rollup property entirely. Click the property header, choose “Delete property.” Confirm deletion. Then add a new rollup property. Click the “+” button, select “Rollup,” and configure it fresh. This clears any stale configuration that may be stuck.
Common Issues After Fixing the Rollup
Rollup shows blank values after changing source type
Changing a property type can cause existing data to become empty. For example, converting a Text property to Number clears all non-numeric text. After the conversion, you need to re-enter numeric values for each row in the related database. Use the “Find and Replace” feature or manually update each entry. The rollup will then display the correct aggregated result.
Rollup returns “NaN” or “Invalid”
The source property contains values that cannot be aggregated. For instance, a Number property may have empty cells or text entries. Ensure every row in the related database has a valid number. Use a formula property to default empty cells to 0: if(empty(prop("Original")), 0, prop("Original")). Then roll up that formula property.
Related database relation breaks after property change
Changing a property type does not break the relation between databases. The relation property is separate from the source property. If the relation itself is missing, you need to recreate the relation link. Go to the original database, edit the rollup, and verify the “Relation” field still points to the correct related database. If not, select the correct relation again.
Rollup Aggregation Functions vs Compatible Source Property Types
| Aggregation Function | Compatible Source Property Types | Incompatible Types That Cause Error |
|---|---|---|
| Sum | Number, Formula (Number) | Text, Select, Date, Checkbox, Email, Phone, URL |
| Average | Number, Formula (Number) | Text, Select, Date, Checkbox, Email, Phone, URL |
| Count All | Any type | None (always works) |
| Count Values | Any type with non-empty values | None, but empty cells are excluded from count |
| Count Unique Values | Any type | None, but duplicates are counted once |
| Count Empty | Any type | None |
| Count Not Empty | Any type | None |
| Percent Empty | Any type | None |
| Percent Not Empty | Any type | None |
| Earliest Date | Date, Formula (Date) | Number, Text, Select, Checkbox, Email, Phone, URL |
| Latest Date | Date, Formula (Date) | Number, Text, Select, Checkbox, Email, Phone, URL |
| Show Original | Any type | None, but shows the first matching value |
The “Rollup cannot be configured” error appears only when the aggregation function and source property type are incompatible. The table above lists every combination. If you see the error, check your aggregation function against the table and adjust the source property type or the function accordingly.