Editing & Saving

Editing Cells

To start editing a cell:

• Double-click the cell
• Press Enter on a focused cell
• Start typing when a cell is focused

Text fields show an input box with a teal outline.

Domain fields (references to parent entities) show a searchable dropdown panel with all available options formatted as {CODE} Name. Type in the search box to filter options by code or name. Use Arrow keys to navigate options and Enter to select. The dropdown header shows the column type and item count.

Boolean fields (e.g., Active/Inactive) show a dropdown with Yes/No/— options in the same modern style.

To save your edit, press Enter, Tab, or click outside the cell. To cancel, press Escape. Clicking outside a dropdown also closes it.

Edited cells are highlighted in yellow until saved.

Saving Changes

When you edit cells, changes are marked as "pending" (yellow highlight). The toolbar shows a Save button with the number of pending changes.

Click Save to open the save dialog:

• A summary of all changes is shown (field, old value → new value)
• Add an optional comment describing the reason for changes
• Press Ctrl+Enter to save, or click the Save button
• Press Escape to cancel

After saving, a confirmation toast appears with an Undo option (available for 10 seconds).

Validation

Primentra validates data at multiple levels to ensure data quality.

Required fields

Every entity has two system fields that are always required:

• Code — the unique business identifier (unless auto-generate is enabled)
• Name — the display name of the record

In addition, any custom attribute can be marked as Required in the entity settings. When a field is required, it must have a non-empty value before the record can be saved.

Visual indicators

• Red border — appears on empty required cells as soon as the row is modified
• Red background — empty required cells get a light red background to draw attention
• "Required" placeholder — empty required cells show "Required" as placeholder text

Once all required fields on the modified row are filled in, the red indicators clear automatically. Completely empty new rows are silently removed when you navigate away.

Save dialog validation

When you click Save, the dialog checks every row in the dataset — not just the rows you changed. If any row has an empty required field:

• The save dialog header turns red with a "Cannot save" message
• A list shows exactly which rows are missing which fields
• The Save button is disabled until all issues are resolved

Duplicate code detection

Code values must be unique within an entity. Duplicate codes are detected in real time:

• Duplicate cells show a red border immediately after editing
• The save dialog lists all rows with duplicate codes
• Saving is blocked until duplicates are resolved

Database-level validation

Required field validation is also enforced at the database level. Even if the frontend validation is bypassed (e.g., via direct API calls), the stored procedure usp_Data_SaveRow checks all required attributes and rejects the save with a descriptive error message.

Undo & Discard

Discard pending changes: Click the Undo button in the toolbar to discard all unsaved changes and revert cells to their original values.

Undo saved changes: Press Ctrl+Z (or Cmd+Z on Mac) to undo the last saved batch of changes. The toast will show which save was undone (including your comment if provided).

The undo stack stores up to 50 previous states per entity.