Editing & Saving
On this page
Edits are made in place, held as pending changes, and written to the database in one batch when you save. Nothing reaches the database until you click Save.
Open a cell
Three ways to start editing:
- Double-click the cell.
- Focus the cell and press Enter.
- Focus the cell and start typing. The first character replaces the old value.
The editors
Each data type gets its own editor.
| Type | Editor |
|---|---|
| Text, Integer, Decimal | An input box with a teal outline |
| Date | An input box with the column's own date mask applied as you type |
| Domain | A searchable list of the referenced records, shown as {CODE} Name. Type in Type to filter… to narrow it, arrow through the options, press Enter to pick one |
| Yes/No | A short list with —, the true label and the false label. The labels follow the column's display format |
To commit, press Enter, Tab, or click another cell. To cancel, press Escape.
Edited cells turn yellow and stay yellow until they are saved.
Save the batch
The header shows Save (N) with the number of pending changes. Click it, or press Ctrl+S (Cmd+S on Mac), to open the save dialog.

The dialog lists every change as field, old value → new value, and marks new records with a NEW badge. Domain values are shown by name, not by row id.
- Read the summary.
- Type an optional audit comment. It is stored with the change and shown in the audit panel.
- Press Ctrl+Enter, or click Save.
Press Escape to close the dialog without saving. Your pending changes stay.
Validation
Required fields
Every entity has two system fields that are always required:
- Code — the unique business identifier. When Auto-generate Code is on, the database assigns it and the cell is read-only
- Name — the display name of the record
Any custom attribute can be marked Required in the entity settings.
An empty required cell in a row you touched gets a red border, a light red background and the placeholder text Required. The markers clear as soon as you fill the field. A new row that is still completely empty is removed when you navigate away.
The save dialog checks every row
When you open the dialog it checks the whole dataset, not only the rows you changed. If a row is incomplete:
- The dialog header turns red and reads Cannot save
- A list names the rows and the missing fields
- The Save button is disabled until the rows are fixed
Duplicate codes
Codes must be unique within an entity. A duplicate gets a red border as soon as you leave the cell, the save dialog lists every clashing code, and saving is blocked. On an auto-code entity this cannot happen, because you never type a code.
The database checks too
usp_Data_SaveRow re-checks every required attribute. A save that bypasses the browser — a direct API call, for example — is still refused with a readable message.
When a colleague changed the same cell
A save sends only the cells you changed. If a colleague saved a change in another column of the same row, that change stays.
If a colleague changed a cell that you also changed, after you loaded it, the save is refused. Nothing is written. The dialog Someone else changed this data opens.

Each line shows one cell:
- The row code and the column, for example
PRD001 · Price. - You saw: the value when you loaded the grid.
- Now: the value in the database.
- Yours: the value you typed.
- Who changed it and when, for example Changed by Iris Hoekstra at 14:02. The name comes from the audit log.
Choose per line
- Use theirs drops your edit of that cell. The cell shows the current value.
- Keep mine keeps your edit. The next save writes it. The audit log then shows the value of your colleague as the old value.
When you have chosen for every line, the dialog says All conflicts are resolved. Press Save to continue. Your other edits are still pending. Press Save again.
If you close the dialog, each cell in conflict keeps a red dashed outline, and all your edits stay pending.
A row that is gone
A colleague can delete a row, or merge it into another row, after you loaded it. The line then says Deleted by Iris Hoekstra at 14:02 or Merged into SUP-1001 by Iris Hoekstra. It has one button: Drop my edits of this row.
What counts as a conflict
- Primentra compares values. If a colleague changed a cell and then changed it back, there is no conflict.
- Paste and undo get the same check as a typed edit.
- Only the grid save has this check. An import, the bulk API, staging, an MDS load and a Lookalikes merge write as before, and the last write wins. An entity with approval uses its own check. See Conflict detection.
- The REST API has the same protection for one record. See REST API.
Undo
Two buttons appear in the header as soon as you have unsaved changes, and they do different things. Both have a keyboard equivalent.
Step back one change. Click Undo, or press Ctrl+Z (Cmd+Z on Mac). Each press reverses one cell edit, one paste or one clear. The cell-level history holds the last 50 steps and is cleared when you save, switch entity, or discard.
Throw away everything. Click Discard all to drop every unsaved change on the screen and restore the original values. This is the same result as leaving the entity without saving.
Related
- Grid Overview: where the Save button lives
- Adding, Deleting & Pasting: new rows and clipboard work
- Audit Panel & Read-Only Fields: read the change history of a row
- Attributes & Data Types: required, unique and decimal settings
- Approval Workflows: what changes when an entity needs approval
Did not find what you need?
Try the troubleshooting pages, or ask us.