Field tablecombo

Version: Pro (advanced-fields).

Why this type

A dropdown. Options load from a MODX class through optionsSource and the mgr/field/options processor, or from a static options list in the schema. This is not a grid. The row grid is table.

The list is empty only when both options and optionsSource are missing. A non-empty static options is used first.

When to use

• A MODX class such as modTemplate
• One row of your own xPDO class, when it has an id and a label field
• When a relation window is not needed

Tips

ModResource picker: relation or combo. Multiple ids: tablemulticombo.

Similar types

• combo for a standard xPDO class
• embeddedTable to render many rows by table_key

Schema

{
  "name": "template",
  "type": "tablecombo",
  "label": "Template",
  "optionsSource": {
    "class": "modTemplate",
    "valueField": "id",
    "labelField": "templatename",
    "limit": 50
  },
  "tab": "Content",
  "width": 100,
  "active": true
}

Value

valueField value.

Section data

Key template in the section data: valueField from optionsSource:

{
  "template": 3
}

Chunk example

modx

[[+template]]

fenom

{if $template}{$template}{/if}

Common properties

For fields with name that are stored in the section data:

Key	Type	Role	CMP
tab	string	Group subtitle in the inspector	yes
width	25, 33, 50, 66, 75, 100	Field width as % of the row (flex). The CMP offers only these values	yes
description	string	Hint under the label	yes
default	any	Initial value for a new section	yes
active	bool	false hides the field in the inspector	yes
required	bool	Required on publish (draft still saves)	yes

See fields overview.

See also

• Field types reference
• Fields overview
• Pro in manager