Record editing takes place in the workspace portion of the user interface.
This action is available only to authorized users in the 'Advanced perspective' or from a specifically configured perspective.
In a tabular view, click the button located above the table.
In a hierarchical view, select 'Create a record' from the menu of the parent node under which to create the new record.
Next, enter the field values in the new record creation form. Mandatory fields are indicated by asterisks.
Double-click the record to update, then edit the field values in the record form.
To discard any changes in progress and restore the fields to their values before editing, click the Revert button.
To duplicate a selected record, select Actions > Duplicate.
A new record creation form pre-populates the field values from the record being duplicated. The primary key must be given a unique value, unless it is automatically generated (as is the case for auto-incremented fields).
To delete one or more selected records, select Actions > Delete.
To compare two selected records, select Actions > Compare.
The content of complex terminal nodes, such as aggregated lists and user defined attributes, are excluded from the comparison process. That is, the compare service ignores any differences between the values of the complex terminal nodes in the records.
In a table, records can be exported to or imported from CSV or XML format.
You can either manually select certain records of the table to export, or you can export the whole table.
When history is enabled on a table, it is possible to restore a record to a previous state, based on its registered history. If the record (identified by its primary key) still exists in the table, it will be updated with the historized values to be restored. Otherwise, it will be created.
In order to restore a record to a previous state, select a record in the history table view, and the select Actions > Restore from history in the workspace. A summary screen is displayed with the details of the update or creation to be performed.
The restore feature is available only on one record at a time.
If a table trigger must have a specific behavior on restore, different from the one on regular create and update, the developer can use the method TableTriggerExecutionContext.isHistoryRestore
.
This feature has limitations linked to the limitations of the history feature:
the 'restore from history' feature is not available on tables containing lists that are not supported by history. See Data model limitations.
computed values, encrypted values and fields on which history has been disabled are ignored when restoring a record from history, since these fields are not historized.
User guide table of contents