> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/release-notes/16-sep-2026-release.md).

# 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.

{% hint style="info" %}
Earlier updates For nested list filters, URL parameter lists, and Reuse / Detach, see the [15 Sep 2026 Release](https://docs.notionapps.com/release-notes/15-sep-2026-release).
{% endhint %}

***

### 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](https://docs.notionapps.com/how-to-guides/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.
```

{% hint style="success" %}
Start here Open **Databases** → **Calculated properties**. Leave **Recalculate in NotionApps** on when the switch is clickable. Publish, then open live Home twice — the number should stay computed, not snap back to `0` / `0/600`.
{% endhint %}

***

### Features

#### 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

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

**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

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

| 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](https://docs.notionapps.com/troubleshooting/some-rollup-properties-do-not-show-up-in-the-app-builder), then Sync |

End users do not see a formula editor. They still see one read-only number.

***

### Related

* [Recalculate calculated properties](https://docs.notionapps.com/how-to-guides/recalculate-calculated-properties)
* [Formulas & Rollups](https://docs.notionapps.com/screens-and-components/formulas-and-rollups)
* [Why are my rollups showing zero or an incorrect value?](https://docs.notionapps.com/troubleshooting/why-are-my-rollups-on-notionapps-showing-zero-0-value-or-an-incorrect-value)
* [Reload and sync](https://docs.notionapps.com/databases/reload-and-sync)
* [📢 Release Notes](https://docs.notionapps.com/release-notes)
* [15 Sep 2026 Release](https://docs.notionapps.com/release-notes/15-sep-2026-release)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notionapps.com/release-notes/16-sep-2026-release.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.