DAM upload field

This DAM upload field definition makes only sense in the context of the Magnolia Assets subapp. Do not use it generically in any other context.

If you work with the Magnolia 5 UI framework, see DAM upload field for Magnolia 5 UI instead.

info.magnolia.dam.app.field.DamUploadFieldDefinition renders a field used by the Magnolia Assets subapp to upload assets to the DAM workspace. It extends UploadFieldDefinition as follows:

  • The uploaded file is mapped to a media type based on its MIME type.

  • Default field labels are overridden by media-type labels such as Upload new image.

  • There are actions for editing images in the media editor and for previewing images.

  • There is a thumbnail preview.

It is possible to configure DamUploadFieldDefinition in dialogs or other apps, but keep in mind that the file will be placed in the workspace for which the field has been configured. For example, if you use the field in a dialog for a component template, that file (when uploaded using the field) will be stored in the website, not the DAM, workspace. It is best practice to keep your assets in the DAM whenever possible and link to them using a link field.

Use info.magnolia.dam.app.field.factory.DamUploadFieldFactory for any custom implementation of the field. If no factory class is configured, the default field will be rendered.

Field properties

Field-specific properties

Property Description


optional, default is ui-mediaeditor:image

Media editor to be used for editing the asset. Use the <module-name>:<media-editor-id> syntax for configuration.


optional, default is image\\/(?!svg\\+xml).*

Regular expression to filter supported files by MIME type. Configuration depends on the value set for the mediaEditorId property.

For digital asset management MIME types, see MediaType.

Common upload field properties

Property Description


optional, default is all types

Comma-separated list of allowed MIME types. Examples include image/*, application/pdf, audio/* and video/*. For a full list, see IANA Media Types.

You can also specify file extensions for each MIME type in the list. This is needed in particular for the application/x-yaml MIME type. In this case, you must also add the file extension: application/x-yaml,.yaml. You don’t need to add extensions for other MIME types.
When allowedMimeTypePattern is defined, a validation message can be configured using the typeAbortMessage property (see Generic i18n keys).


optional, default is 2^63 (9.2 EB)

Maximum file size in bytes.

When maxUploadSize is defined, a validation message must be configured using the sizeAbortMessage property (see Generic i18n keys).

Common simple field properties

Property Description



Name of the field definition item. Derived from the configured node name. Use alphanumeric characters without spaces.


required (unless $type is used)

Type of the field definition item. The value must be a fully qualified class name and a subtype of info.magnolia.ui.field.FieldDefinition. See Field types for possible values.


You can use this as a shortcut for class if the definition class is annotated with info.magnolia.ui.field.FieldType. The proper value is defined by the annotation.

Example class annotation
public class TextFieldDefinition extends ConfiguredFieldDefinition<String> {

See Field types for possible values.



Property type of the field.

A default type is typically hard-coded in each definition class. You only need to add this property if you want to override the default implementation.

In text fields, make sure that type has a value matching the type of data you entered (for example, java.lang.Long for long values) and that converterClass is set accordingly.

Example definition
  $type: textField
  type: java.lang.Long
  converterClass: com.vaadin.data.converter.StringToLongConverter

You can’t configure this property through YAML but it can be used in your Java code.



Converts values between the presentation (UI) and model (stored data). The property must extend com.vaadin.data.Converter. Available classes:

  • info.magnolia.ui.editor.converter.JcrNodeToIdentifierConverter

  • info.magnolia.ui.editor.converter.JcrNodeToPathConverter

  • info.magnolia.ui.editor.converter.JcrNodeToWorkspaceAndIdConverter

  • info.magnolia.ui.editor.converter.JcrPathToIdentifierConverter

com.vaadin.data.converter.StringToBigDecimalConverter and com.vaadin.data.converter.StringToDoubleConverter always round the presentation value by default. For non-rounding converters, use the following classes instead:

  • info.magnolia.ui.field.converter.NonRoundingStringToBigDecimalConverter

  • info.magnolia.ui.field.converter.NonRoundingStringToDoubleConverter

You can’t configure this property through YAML but it can be used in your Java code.


optional, default is translated conversion.message.error key

Message shown when there is an error in the conversion process. The value can be literal or a key of a message bundle.



Pre-filled default value displayed in the field. The value can be overwritten by the user. Use alphanumeric characters.

This is only applied only when creating a new item, not for existing items.

For defaultValue to work, the populate property in info.magnolia.ui.dialog.actions.OpenDialogActionDefinition must be set to false.



Help text displayed when the user clicks the help icon. The value can be literal or a key of a message bundle.



Defines the factory class that initializes and builds the Vaadin form field. The default factory class depends on the particular field.

The value must be a fully qualified class name and a subtype of info.magnolia.ui.field.FieldFactory.

You can’t configure this property through YAML but it can be used in your Java code.



Defines the binder class that applies configuration parameters from the field.


optional, default is false

Enables i18n authoring support, which allows editors to write foreign-language or regionally targeted content. A two-letter language identifier (en, de, fr, etc.) is displayed on controls where i18n is set to true.



Field label displayed to editors. The value can be literal or a key of a message bundle.

If you do not provide the property, Magnolia will fall back to a generated i18n key.

If you do not want to have any label, set the property to an empty string such as label: "" in YAML.


optional, default is false

Makes the field uneditable.


optional, default is false (not relevant for checkbox field)

Makes the field required. When true, an asterisk is displayed next to the field label.

When false, empty values are accepted as valid. For those empty values, any field validators are ignored.


optional, default is translated validation.message.required key

Error message shown when required is set to true and the user saves an empty field. The value can be literal or a key of a message bundle.



Additional style information for an editor property definition item applied to the element when the form is rendered. The value can be a CSS class or a list of CSS classes separated by white spaces.

The style name will be rendered as an HTML class name, which can be used in a CSS definition. The class name is added to the field by calling the Vaadin method addStyleName.

The referenced class can be defined in:



List of field validator definition items. Any value must be a subtype of info.magnolia.ui.field.FieldValidatorDefinition.

See Field validators for more information.


DX Core



This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules
6.3 beta

Magnolia 6.3 beta

Magnolia 6.3 is in beta. We are updating docs based on development and feedback. Consider the 6.3 docs currently in a state of progress and not final.

We are working on some 6.3-beta known issues during this phase.