Setup: guides

Create a field

  1. Open Data model › Fields and choose New field. The dialog asks only for the field type and name; the details of the field open afterwards.

  2. Choose the field type. These questions help:

    1. Will you filter, sort or group by the value? Then pick a field type with a matching storage form: a date as Date , a number as Number , not as text.
    2. Is the set of values limited? Then a Select list .
    3. Is it hierarchical? Then a Selection tree or a Hierarchical select list .
    4. Does an entry repeat with an addition (a dimension per reference, a title per language)? Then a JSON field .

    If you would like advice, use the icon Copy prompt for creating a field next to Field type, see below .

  3. Under Basics, check the Field name. Filters, templates and exports refer to the field by this name. No units, no project names, no years, no typographic quotation marks.

  4. Set the Field group. It orders the field selections. A prefix per area sorts them automatically.

  5. Enter a Note and Sample content. The note appears next to the field during data entry. The layout editor shows the sample content in place of real values.

  6. Enter the configuration under Parameters. Next to it you see the Field type default. With apply you copy its keys into your own configuration and then change only what should differ.

  7. Under Permissions, set the Read and write permissions for Everyone and per group. See below.

  8. Place the field on a layout . Otherwise it is not visible anywhere during data entry.

Field details of the number field “Datierung von” (dated from, field type INT): on the left the sections Basics, Parameters, Output, Conditions, Permissions and Usage, in the middle the Parameters section with units and input form, on the right the description of the field type with the box “Field type default” and the “apply” button.

Have an AI draft a field and a value list

Two icons (asterisks) place a ready-made request for a language model of your choice on the clipboard. At the very top there is an empty line AUFGABE (task) for the sentence only you know. Moliri sends nothing to a language model; you copy the answer back by hand.

WhereWhat the request containsWhat comes back
Dialog New field, next to Field type: Copy prompt for creating a fieldAll field types with their parameters, plus the existing fields, so that the model reuses a suitable one instead of suggesting a duplicateField name, field type and the configuration as JSON for Parameters
Field details, Parameters, at Options (select list, selection tree, hierarchical select list) or Fixed suggestions (text): Copy prompt for the value listThe current list, for a selection tree also the level separator, and the instruction not to rename existing valuesThe list, one entry per line

Moliri treats the pasted answer like anything you type yourself. Whether the field type and the values make sense for your collection is your decision.

Set permissions correctly

GoalSetting
Everyone may editEveryone: Edit
Everyone may readEveryone: Read only
Only certain groupsEveryone: No access, plus each group individually

A group’s permission and the permission for everyone are combined, and the higher one applies. Project and layout set an upper limit on the result: in a project that someone may only read, they cannot edit any field. See Permission model .

Permissions also apply in the full-text search. A field that someone may not read gives them neither hits nor a text excerpt there, not even via comment and source. Purchase prices or insurance values thus stay hidden from everyone the field is not shared with. For a file field this also covers the files in it: whoever may not read the field does not see them in the object’s file area and cannot retrieve them.

Your own configuration replaces the default

If a field has a configuration of its own, it applies instead of the field type default, not in addition to it. If you only want to add units to a number field, first apply the default and then make your changes.

A wrong key name is silently ignored

An unknown or misspelt setting produces no error message. If a setting has no effect, check the key name first. The keys of each field type are listed under Field types .

Avoid renaming

Instead of changing the field name, change the label on the layout. You can choose it freely per layout, and it breaks nothing.

If the name has to change after all, Moliri updates the saved Word templates to the new name in the background. Anything it could not rewrite is reported afterwards in a warning with a report. For other places that refer to the field by its name, see Fields .

Retire a field

Fields cannot be deleted in the interface. To retire a field you no longer need, remove it from the layouts and set the permissions for Everyone to No access, with no group. For accounts with status 3 it disappears from layouts and field selections, its values remain, and the decision can be reversed.

Further reading