Data editor
The data editor lets you edit tables of the invoiceR database directly in invoiceR, above all master data: create, change and complete entries. In principle, any table of the invoiceR database can be enabled for the editor.
Working in the editor
Section titled “Working in the editor”Enabled tables appear in the main menu under Master data. The editor shows the data as a table:
- Click a row. The matching input field appears directly in the cell.
- Change the values you want. All changes are buffered and can be undone.
- Click Save. Only now are the changes saved.
Whether new rows can be created and rows deleted depends on the configuration.
Permissions
Section titled “Permissions”| Permission | Effect |
|---|---|
Pages.MasterDataEditor | view master data in the editor |
Pages.MasterDataEditor.Edit | edit master data in the editor |
Access can also be restricted to roles per table (see below).
Enabling a table
Section titled “Enabling a table”Which tables appear in the editor is stored in conf.EditableEntities. Each row is a menu entry under
Master data.
| Column | Meaning |
|---|---|
ClassIdentifier | full class name of the entity, and so indirectly the table. Example: web_manager.Mstr.AdditionalData |
Title | text of the menu entry |
Description | description shown on the editor page |
MenuOrder | order in the menu. Entries without a value follow, sorted by name. |
MenuIconClass | icon of the menu entry, for example fas fa-vector-square |
FormId | Id of the form in conf.AccountingForms that defines the editable fields |
VisibleFilterRoleId | role that may see the table |
EditFilterRoleId | role that may edit the table |
StaticFilterProperty | property for a fixed filter. Navigation is possible, for example AdditionalDataType.Description. |
StaticFilterValue | value for the fixed filter. It is enough for the property to contain the value. |
AllowCreateDelete | whether rows may be created and deleted |
DefaultPropertyValues | JSON list with default values for new rows |
OuBindingType | whether and how an organization unit is given per row: 0 not needed, 1 optional, 2 mandatory, 3 optional without root entry, 4 mandatory without root entry |
You define the editor’s fields the same way as for an accounting form: through conf.AccountingForms,
conf.AccountingFormFields and conf.AccountingFields. See Configuring accounting
and Accounting fields.
