Skip to content

Renaming columns

Renaming a column posts to /admin/tables/rename and calls RenameColumnAlias on the backend. It changes the column’s public alias, not its physical storage name, and the rename is recorded in the rename history.

The form carries the selection and the rename:

  • profile and table — hidden fields identifying the table;
  • old_column_name — the column to rename;
  • new_column_name — the new public name.

Both names are required; a missing side is refused with 422 before the backend is called. The new name is trimmed before posting.

Only columns the backend marks renameable are offered as targets. Provenance and renameability are separate properties: accounting companion columns remain renameable, while protected generated columns (such as the phone and IBAN companions) do not. The page lists the renameable columns and renders each column’s badges — currency, rounding, quantity ledger, read-only, and its generated from source.

A successful rename answers with the page re-read from the backend, so the column list reflects the new name. The rename is appended to the alias history readable at /admin/profiles/history.