The display conditions are implemented in class TYPO3\\CMS\\Backend\\Form\\FormDataProvider\\EvaluateDisplayConditions, which is a FormDataProvider. It can be used for fields directly in the record as well as for FlexForm values.

string / array

Contains one or more condition rules for whether to display the field or not.

Conditions can be grouped and nested using boolean operators AND or OR as array keys. See examples below.

A rule is a string divided into several parts by ":" (colons). The first part is the rule-type and the subsequent parts depend on the rule type.

The following rules are available:


This evaluates based on another field's value in the record.

  • Part 1 is the field name
  • Part 2 is the evaluation type. These are the possible options:

    Requires the field to have a "true" value. False values are "" (blank string) and 0 (zero). Everything else is true. For the REQ evaluation type Part 3 of the rules string must be the string "true" or "false". If "true" then the rule returns "true" if the evaluation is true. If "false" then the rule returns "true" if the evaluation is false.
    > / < / >= / <=
    Evaluates if the field value is greater than, less than the value in "Part 3"
    = / !=
    Evaluates if the field value is equal to value in "Part 3"
    IN / !IN
    Evaluates if the field value is in the comma list equal to value in "Part 3"
    - / !-
    Evaluates if the field value is in the range specified by value in "Part 3" ([min] - [max])
    BIT / !BIT
    Evaluates if the bit specified by the value in "Part 3" is set in the field's value (considered as an integer)
  • Part 3 is a comma separated list of string or numeric values
This will show the field for new records which have not been saved yet.
This will show the field for existing records which have already been saved.
This will hide the field for all non-admin users while admins can see it. Useful for FlexForm container fields which are not supposed to be edited directly via the FlexForm but rather through some other interface.

userFunc call with a fully qualified class name.

Additional parameters can be passed separated by colon: USER:Evoweb\\Example\\User\\MyConditionMatcher->checkHeader:some:more:info

The following arguments are passed as array to the userFunc:

  • record: the currently edited record
  • flexContext: details about the FlexForm if the condition is used in one
  • flexformValueKey: vDEF
  • conditionParameters: additional parameters

The called method is expected to return a bool value: true if the field should be displayed, false otherwise.


Evaluate if a record is a "versioned" record from workspaces.

  • Part 1 is the type:

    Part 2 is "true" or "false": If true, the field is shown only if the record is a version (pid == -1). Example to show a field in "Live" workspace only: VERSION:IS:false

In FlexForm, display conditions can be attached to single fields in sheets, to sheets itself, to flex section fields and to flex section container element fields. FIELD references can be prefixed with a sheet name to reference a field from a neighbor sheet, see examples below.


Simple display condition

This example will require the field named "tx_templavoila_ds" to be true, otherwise the field for which this rule is set will not be displayed:

'displayCond' => 'FIELD:tx_templavoila_ds:REQ:true',

Combining conditions

Multiple conditions can be combined:

'displayCond' => [
    'AND' => [

An example with multiple values and OR:

$GLOBALS['TCA']['tx_mask_table']['columns']['tx_mask_field']['displayCond']['OR'] = [

This is the same as:

= 'FIELD:tx_mask_otherfield:IN:1,2,4';

A complex example

Going further the next example defines the following conditions: for the "example_field" field to be displayed, the content element must be in the default language. Furthermore it must be a text-type element or have the headline "Example" defined:

'displayCond' => [
    'AND' => [
        'OR' => [

A complex example in a FlexForm

Using OR and AND within FlexForms works like this:


Access values in a flexform

Flex form fields can access field values from various different sources:

<!-- Hide field if value of record field "header" is not "true" -->
<!-- Hide field if value of parent record field "field_1" is not "foo" -->
<!-- Hide field if value of neighbour field "flexField_1 on same sheet is not "foo" -->
<!-- Hide field if value of field "flexField_1" from sheet "sheet_1" is not "foo" -->