MM

MM (type => select)

Path

$GLOBALS['TCA'][$table]['columns'][$field]['config']

Type

string (table name)

Scope

Proc.

This value contains the name of the table in which to store an MM relation. It is used together with foreign_table.

The database field with a MM property only stores the number of records in the relation.

There is additional information in the MM common property description.

Examples

Select field with foreign table via MM table

EXT:styleguide/Configuration/TCA/tx_styleguide_elements_select.php

[
    'columns' => [
        'select_single_15' => [
            'label' => 'select_single_15 foreign_table',
            'config' => [
                'type' => 'select',
                'renderType' => 'selectSingle',
                'foreign_table' => 'tx_styleguide_staticdata',
                'MM' => 'tx_styleguide_elements_select_single_15_mm',
            ],
        ],
    ],
]

Related configurations

MM_hasUidField (type => select)

Path

$GLOBALS['TCA'][$table]['columns'][$field]['config']

Type

boolean

Scope

Proc.

If the multiple property is set with MM relations you must set this value to true and include a UID field. Otherwise sorting and removing relations will be buggy.

MM_insert_fields (type => select)

Deprecated since version 12.4: As there is no API to retrieve these values again, having a static value in an additional column is useless. Therefore, this setting is removed in TYPO3 v13. More details

Path

$GLOBALS['TCA'][$table]['columns'][$field]['config']

Type

array

Scope

Proc.

Array of field=>value pairs to insert when writing new MM relations.

MM_match_fields (type => select)

Path

$GLOBALS['TCA'][$table]['columns'][$field]['config']

Type

array

Scope

Display / Proc.

Array of field=>value pairs to both insert and match against when writing/reading MM relations.

MM_opposite_field (type => select)

Path

$GLOBALS['TCA'][$table]['columns'][$field]['config']

Type

string (field name)

Scope

Proc.

If you want to make a MM relation editable from the foreign side (bidirectional) of the relation as well, you need to set MM_opposite_field on the foreign side to the field name on the local side.

For example if the field "companies.employees" is your local side and you want to make the same relation editable from the foreign side of the relation in a field called persons.employers, you would need to set the MM_opposite_field value of the TCA configuration of the persons.employers field to the string "employees".

Note

Bidirectional references only get registered once on the native side in "sys_refindex".

MM_oppositeUsage (type => select)

Path

$GLOBALS['TCA'][$table]['columns'][$field]['config']

Type

array

Scope

Proc.

In a MM bidirectional relation using group match fields the opposite side needs to know about the match fields for certain operations (for example, when a copy is created in a workspace) so that relations are carried over with the correct information.

MM_oppositeUsage is an array which references which fields contain the references to the opposite side, so that they can be queried for match field configuration.

MM_table_where (type => select)

Path

$GLOBALS['TCA'][$table]['columns'][$field]['config']

Type

string (SQL WHERE)

Scope

Proc.

Additional where clause used when reading MM relations.

Example:

{#uid_local} = ###THIS_UID###

The above example uses the special field quoting syntax {#...} around identifiers of the QueryHelper to be as DBAL compatible as possible.