16 Sep 2026 Release
NotionApps can now recalculate Notion formula and rollup properties from the recipe Notion already defined. You do not type a formula. A per-field Recalculate in NotionApps toggle decides whether Home keeps our number or Notion’s page API.
What’s new at a glance
Section titled “What’s new at a glance”| Capability | What you can do | Learn more |
|---|---|---|
| Calculated properties | See every formula and rollup on Databases, with a count of fields we cannot recalculate | Recalculate calculated properties |
| Recalculate toggle | Leave on so Home uses our eval; off = Notion’s raw page value; disabled = we cannot eval yet | Same how-to |
| Read-only recipe | Inspect Notion’s expression or rollup function without editing it here | Same how-to |
| Keep a good number | After a successful compute, published Home does not fulfill that field from Notion again | Same how-to |
You do not write formulas in NotionApps.On = our eval of Notion's recipe. Off = Notion's page leaf.Disabled means we cannot evaluate it yet.Features
Section titled “Features”1. Calculated properties on Databases
Section titled “1. Calculated properties on Databases”The Databases tab lists formula and rollup fields only. Each database shows a caption such as 3 formulas, 2 rollups — 4 cannot recalculate. Apps with no calculated properties do not show the section.
You never type a formula here. Notion still owns the recipe. Change the expression in Notion, then Sync from Notion.
2. Recalculate in NotionApps
Section titled “2. Recalculate in NotionApps”On each evaluable field:
| Toggle | Published app |
|---|---|
| On | We evaluate the recipe. Home keeps that number. |
| Off | Screens show Notion’s page API value. |
| Disabled | We cannot evaluate this recipe. Notion keeps the number. A reason names the unsupported token or missing rollup recipe. |
Evaluable fields start on. Existing apps keep that default so simple prop() heals do not regress.
Status lines:
- We’ll recalculate this
- Using Notion’s value
- Waiting on related fields
- Can’t recalculate
3. What we can evaluate today
Section titled “3. What we can evaluate today”Formulas: prop(), + - * /, if(), dateBetween, and simple literals (including a /600 ratio suffix).
Rollups: sum, count, average, min, max, once the rollup recipe is loaded.
Not yet: formatDate, ifs, lets, style, map, filter, join, empty, includes, length, format, and other rollup functions. Sync can load a missing rollup recipe. Sync does not unlock those tokens.
4. Home no longer overwrites a good compute
Section titled “4. Home no longer overwrites a good compute”The bug this release closes: we computed a real number, left the field incomplete, then Home fulfilled Notion’s 0 / 0/600 leaf and looked blank again.
When Recalculate is on and the compute succeeded, that field is not fulfilled from Notion again.
What makers need to change
Section titled “What makers need to change”| Goal | Extra work |
|---|---|
| Keep current formula/rollup display | None if the toggle is on (the default when we can evaluate) |
Trust Home for simple prop() math or sum/count/average/min/max |
Leave Recalculate on; Publish; open live Home twice |
| Show Notion’s raw page value | Turn Recalculate off |
Unsupported formatDate / ifs formulas |
Nothing — Notion keeps the number. The reason explains why. |
| Missing rollup recipe | Sync from Notion, then reopen Calculated properties |
| Related database not shared | Grant access, then Sync |
End users do not see a formula editor. They still see one read-only number.