See also: Blob field

Quick info

A complex (composite) field to store a file with meta information.
The file content is stored in the file system via the StorageManager.

The field is available only if the document module is licensed.

This creates 3 columns in the entity table:

Name	Column	Type
myFile.name	my_file_name	VARCHAR(255)
myFile.contentType	my_file_content_type	VARCHAR(255)
myFile.size	my_file_size	BIGINT

►NOTE◄ When reading the header data, the content of the file is not loaded automatically. This is done automatically by reading the 'content' field ( file field) on the server side.

On the client side, the file can also be reloaded via the "downloadUrl" field. However, session cookies must be allowed for this, as the link can only be loaded with a valid user session with the necessary read rights for the associated object.

This prevents data sets containing files from being unnecessarily large during loading/editing and files from being specifically reloaded only when they are actually needed.

File field in overviews and tuple searches

The content of the file cannot be resolved if the file field was only loaded via a tuple search (e.g. overviews). On the client side, however, the link (downloadUrl) can easily be generated by the user: DOC/document/content/TYPNAME/FIELDNAME/ENTITY_ID.
In the list settings of an overview, the download url is also available as a preconfigured column (fieldname.downloadUrl). This data field can consequently also be bound directly in own display types.