Update an installed app
What installing a newer version of an app changes, what it always keeps, and when an update is held back.
When the gallery has a newer version of an app you installed, its card is tagged Update available, and its page shows the version here and the one available. An update installs the newer version over yours. It adds what is missing and refreshes some definitions. It never removes anything, and adds no rows.
Update an app
- Open the app's page from the gallery.
- Read the list headed What … changes, with the new version's number in it. It shows each page and form the new version adds (as a draft), each table, view, role and column it adds, and the views marked definitions refreshed.
- Under it, Kept as they are says what stays, counted where the app names its rows: for example "your 52 products, 38 offers and anything you added".
- Choose Update to …, which names the new version.
A message says the app was updated, and to which version.
What an update refreshes
| What | What happens |
|---|---|
| The app's views | Each view's definition (which rows, the grouping and totals, the sort) is rewritten to the new version's, replacing any change you made to it. |
| Layouts the app sets | Where the app lays a view or table out, for example Catalogue as Cards, that layout is set again. So is the note an app shows under a summary. |
| The app's roles | Each role gets every permission the new version gives it, including one you took away. Permissions you added stay. |
| Missing parts | A table, view or column the new version makes that is not here under its name is made, empty. That includes one you deleted, and a column you renamed: the app adds a new, empty one under its own name. |
What an update always keeps
- Every row, your own and the sample rows.
- The pages and forms the app made, exactly as you left them, published or not. Only pages new in this version are added, as drafts.
- Everything you added: fields, tables, views, pages, roles and who is in them.
- Anything the new version no longer makes. It stays where it is; an update removes nothing.
An update cannot be undone, and there is no way back to an earlier version. If you edited the app's views or its roles' permissions, read the table above before you update.
When an update is held back
It would make a second copy
This install's “Offer Products”, “Offer Clients”, “Offer Lines”, “Offer Catalogue” and “Offer Totals” are not in version 3.0.0. An update can't rename a table yet, so version 2.0.0 stays here and keeps working as it is.
An update finds the app's tables, views and pages by name. When the new version names one differently from the one here, it would make a new, empty table beside yours, while the app's pages kept reading the old one. So the update is not offered at all: the card shows Installed, and the app's page says why. Nothing is wrong with what you have.
That is the message on a workspace holding Product catalogue and offers 2.0.0. Installs of the earlier versions of the four built-in apps, whose table names began with Offer, CRM, Trial or Comp, are held back this way. It also happens when you rename a table, view or page the app made and a newer version still uses the app's name for it; renaming yours back to that name lets the update be offered.
It stores a column differently
Version … is installed here. Version … stores some of its columns differently (…), and updating an older install is not available yet. Nothing in this workspace will change.
The new version makes a column a different kind from the one here, for example a link to another table where yours is text. The brackets name each such column as table and column. This also happens if you changed one of the app's columns into another kind. Update to cannot be pressed. If the column is one you changed, change it back to let the update go ahead.
Something else is in the way
An update meets the same checks as an install: names you already use for something else, and your permissions. See When an app can't be installed here.
Last updated 29 October 2026