Form Types

Admin related form types

When defining fields in your admin classes you can use any of the standard Symfony field types and configure them as you would normally. In addition there are some special Sonata field types which allow you to work with relationships between one entity class and another.

Sonata\AdminBundle\Form\Type\ModelType

This type allows you to choose an existing entity from the linked model class. In effect it shows a list of options from which you can choose a value (or values).

For example, we have an entity class called Page which has a field called image1 which maps a relationship to another entity class called Image. All we need to do now is add a reference for this field in our PageAdmin class:

// src/Admin/PageAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use Sonata\AdminBundle\Form\Type\ModelType;

final class PageAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $imageFieldOptions = []; // see available options below

        $formMapper
            ->add('image1', ModelType::class, $imageFieldOptions)
        ;
    }
}

Note that the third parameter to FormMapper::add() is optional so there is no need to pass in an empty array, it is shown here only to demonstrate where the options go when you want to use them.

Since the image1 field refers to a related entity we do not need to specify any options. Sonata will calculate that the linked admin class is of type Image and, by default, use the ImageAdmin class to retrieve a list of all existing Images to display as choices in the selector.

Tip

You need to create ImageAdmin class in this case to use sonata_type_model type. You can also use <form_types_fielddescription_options> use the admin_code parameter.

The available options are:

property: defaults to null. You can set this to a Symfony PropertyPath compatible string to designate which field to use for the choice values.
query: defaults to null. You can set this to a ProxyQueryInterface instance in order to define a custom query for retrieving the available options.
template: defaults to 'choice' (not currently used?)
multiple: defaults to false - see the Symfony choice Field Type docs for more info
expanded: defaults to false - see the Symfony choice Field Type docs for more info
choices: defaults to null - see the Symfony choice Field Type docs for more info
preferred_choices: defaults to [] - see the Symfony choice Field Type docs for more info
choice_loader: defaults to a ModelChoiceLoader built from the other options
model_manager: defaults to null, but is actually calculated from the linked admin class. You usually should not need to set this manually.
class: The entity class managed by this field. Defaults to null, but is actually calculated from the linked admin class. You usually should not need to set this manually.
btn_add, btn_list, btn_delete and btn_catalogue:: The labels on the add, list and delete buttons can be customized with these parameters. Setting any of them to false will hide the corresponding button. You can also specify a custom translation catalogue for these labels, which defaults to SonataAdminBundle.

Note

An admin class for the linked model class needs to be defined to render this form type.

Note

If you need to use a sortable Sonata\AdminBundle\Form\Type\ModelType check the ../cookbook/recipe_sortable_sonata_type_model page.

Note

When using Sonata\AdminBundle\Form\Type\ModelType with btn_add, a jQuery event will be triggered when a child form is added to the DOM (sonata-admin-setup-list-modal by default and sonata-admin-append-form-element when using edit:inline).

Sonata\AdminBundle\Form\Type\ModelListType

This type allows you to choose an existing entity, add a new one or edit the one that is already selected.

For example, we have an entity class called Page which has a field called image1 which maps a relationship to another entity class called Image. All we need to do now is add a reference for this field in our PageAdmin class:

// src/Admin/PageAdmin.php

use Sonata\AdminBundle\Form\Type\ModelListType;
use Sonata\AdminBundle\Form\FormMapper;

final class PageAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $formMapper
            ->add('image1', ModelListType::class)
        ;
    }
}

The available options are:

model_manager: defaults to null, but is actually calculated from the linked admin class. You usually should not need to set this manually.
class: The entity class managed by this field. Defaults to null, but is actually calculated from the linked admin class. You usually should not need to set this manually.
btn_add, btn_edit, btn_list, btn_delete and btn_catalogue:: The labels on the add, edit, list and delete buttons can be customized with these parameters. Setting any of them to false will hide the corresponding button. You can also specify a custom translation catalogue for these labels, which defaults to SonataAdminBundle.

Note

For more info, see the storage-engine-specific form field definitions: ORM, PHPCR, MongoDB

Sonata\AdminBundle\Form\Type\ModelHiddenType

The value of hidden field is identifier of related entity:

// src/Admin/PageAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use Sonata\AdminBundle\Form\Type\ModelHiddenType;

final class PageAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        // generates hidden form field with id of related Category entity
        $formMapper
            ->add('categoryId', ModelHiddenType::class)
        ;
    }
}

The available options are:

model_manager: defaults to null, but is actually calculated from the linked admin class. You usually should not need to set this manually.
class: The entity class managed by this field. Defaults to null, but is actually calculated from the linked admin class. You usually should not need to set this manually.

Sonata\AdminBundle\Form\Type\ModelAutocompleteType

This type allows you to choose an existing entity from the linked model class. In effect it shows a list of options from which you can choose a value. The list of options is loaded dynamically with ajax after typing 3 chars (autocomplete). It is best for entities with many items.

This field type works by default if the related entity has an admin instance and in the related entity datagrid is a string filter on the property field.

For example, we have an entity class called Article (in the ArticleAdmin) which has a field called category which maps a relationship to another entity class called Category. All we need to do now is add a reference for this field in our ArticleAdmin class and make sure, that in the CategoryAdmin exists datagrid filter for the property title:

// src/Admin/ArticleAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use Sonata\AdminBundle\Form\Type\ModelAutocompleteType;

final class ArticleAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        // the dropdown autocomplete list will show only Category
        // entities that contain specified text in "title" attribute
        $formMapper
            ->add('category', ModelAutocompleteType::class, [
                'property' => 'title'
            ])
        ;
    }
}

// src/Admin/CategoryAdmin.php

use Sonata\AdminBundle\Datagrid\DatagridMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;

final class CategoryAdmin extends AbstractAdmin
{
    protected function configureDatagridFilters(DatagridMapper $datagridMapper)
    {
        // this text filter will be used to retrieve autocomplete fields
        $datagridMapper
            ->add('title')
        ;
    }
}

The available options are:

property

defaults to null. You have to set this to designate which field (or a list of fields) to use for the choice values. This value can be string or array of strings.

class

The entity class managed by this field. Defaults to null, but is actually calculated from the linked admin class. You usually should not need to set this manually.

model_manager

defaults to null, but is actually calculated from the linked admin class. You usually should not need to set this manually.

callback

defaults to null. Callable function that can be used to modify the query which is used to retrieve autocomplete items. The callback should receive three parameters - the admin instance, the property (or properties) defined as searchable and the search value entered by the user.

From the $admin parameter it is possible to get the Datagrid and the Request:

$formMapper
    ->add('category', ModelAutocompleteType::class, [
        'property' => 'title',
        'callback' => static function (AdminInterface $admin, string $property, $value): void {
            $datagrid = $admin->getDatagrid();
            $query = $datagrid->getQuery();
            $query
                ->andWhere($query->getRootAlias() . '.foo=:barValue')
                ->setParameter('barValue', $admin->getRequest()->get('bar'))
            ;
            $datagrid->setValue($property, null, $value);
        },
    ])
;

If you want to dynamically change the property being filtered on to something else, you can use a prefix system, as follows. When the user types id: 20 the property used for filtering is "id". When they type username: awesome_user_name, it will be "username":

$formMapper
    ->add('category', ModelAutocompleteType::class, [
        'property' => 'title',
        'callback' => static function (AdminInterface $admin, string $property, string $value): void {
            $datagrid = $admin->getDatagrid();

            $valueParts = explode(':', $value);
            if (count($valueParts) === 2 && in_array($valueParts[0], ['id', 'email', 'username'])) {
                [$property, $value] = $valueParts;
            }

            $datagrid->setValue($datagrid->getFilter($property)->getFormName(), null, $value);
        },
    ])
;

to_string_callback

defaults to null. Callable function that can be used to change the default toString behavior of entity:

$formMapper
    ->add('category', ModelAutocompleteType::class, [
        'property' => 'title',
        'to_string_callback' => function($entity, $property) {
            return $entity->getTitle();
        },
    ])
;

response_item_callback

defaults to null. Callable function that can be used to customize each item individually returned in JSON:

$formMapper
    ->add('category', ModelAutocompleteType::class, [
        'property' => 'title',
        'response_item_callback' => function (AdminInterface $admin, object $entity, array $item): array {
            $item['type'] = $entity->getType();

            return $item;
        },
    ])
;

multiple

defaults to false. Set to true, if your field is in a many-to-many relation.

placeholder

defaults to "". Placeholder is shown when no item is selected.

minimum_input_length

defaults to 3. Minimum number of chars that should be typed to load ajax data.

items_per_page

defaults to 10. Number of items per one ajax request.

quiet_millis

defaults to 100. Number of milliseconds to wait for the user to stop typing before issuing the ajax request.

cache

defaults to false. Set to true, if the requested pages should be cached by the browser.

url

defaults to "". Target external remote URL for ajax requests. You usually should not need to set this manually.

route

The route name with parameters that is used as target URL for ajax requests.

width

defaults to "". Controls the width style attribute of the Select2 container div.

dropdown_auto_width

defaults to false. Set to true to enable the dropdownAutoWidth Select2 option, which allows the drop downs to be wider than the parent input, sized according to their content.

container_css_class

defaults to "". Css class that will be added to select2's container tag.

dropdown_css_class

defaults to "". CSS class of dropdown list.

dropdown_item_css_class

defaults to "". CSS class of dropdown item.

safe_label

defaults to false. Set to true to enable the label to be displayed as raw HTML, which may cause an XSS vulnerability.

req_param_name_search

defaults to "q". Ajax request parameter name which contains the searched text.

req_param_name_page_number

defaults to "_page". Ajax request parameter name which contains the page number.

req_param_name_items_per_page

defaults to "_per_page". Ajax request parameter name which contains the limit of items per page.

template

defaults to @SonataAdmin/Form/Type/sonata_type_model_autocomplete.html.twig. Use this option if you want to override the default template of this form type.

btn_add and btn_catalogue:

The labels on the add button can be customized with these parameters. Setting any of them to false will hide the corresponding button. You can also specify a custom translation catalogue for these labels, which defaults to SonataAdminBundle:

// src/Admin/ArticleAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use Sonata\AdminBundle\Form\Type\ModelAutocompleteType;

final class ArticleAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $formMapper
            ->add('category', ModelAutocompleteType::class, [
                'property' => 'title',
                'template' => '@App/Form/Type/sonata_type_model_autocomplete.html.twig',
            ])
        ;
    }
}

{# templates/Form/Type/sonata_type_model_autocomplete.html.twig #}

{% extends '@SonataAdmin/Form/Type/sonata_type_model_autocomplete.html.twig' %}

{# change the default selection format #}
{% block sonata_type_model_autocomplete_selection_format %}'<b>'+item.label+'</b>'{% endblock %}

{# customize select2 options #}
{% block sonata_type_model_autocomplete_select2_options_js %}
options.multiple = false;
options.dropdownAutoWidth = false;
{% endblock %}

target_admin_access_action

defaults to list. By default, the user needs the LIST role (mapped to list access action) to get the autocomplete items from the target admin's datagrid. If you can't give some users this role because they will then have access to the target admin's datagrid, you have to grant them another role.

In the example below we changed the target_admin_access_action from list to autocomplete, which is mapped in the target admin to AUTOCOMPLETE role. Please make sure that all valid users have the AUTOCOMPLETE role:

// src/Admin/ArticleAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use Sonata\AdminBundle\Form\Type\ModelAutocompleteType;

final class ArticleAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        // the dropdown autocomplete list will show only Category
        // entities that contain specified text in "title" attribute
        $formMapper
            ->add('category', ModelAutocompleteType::class, [
                'property' => 'title',
                'target_admin_access_action' => 'autocomplete',
            ])
        ;
    }
}

You have to modify the target entity in the following way:

// src/Admin/CategoryAdmin.php

use Sonata\AdminBundle\Datagrid\DatagridMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;

final class CategoryAdmin extends AbstractAdmin
{
    protected $accessMapping = [
        'autocomplete' => 'AUTOCOMPLETE',
    ];

    protected function configureDatagridFilters(DatagridMapper $datagridMapper)
    {
        // this text filter will be used to retrieve autocomplete fields
        // only the users with role AUTOCOMPLETE will be able to get the items
        $datagridMapper
            ->add('title')
        ;
    }
}

Sonata\AdminBundle\Form\Type\ChoiceFieldMaskType

According the choice made only associated fields are displayed. The others fields are hidden:

// src/Admin/AppMenuAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use Sonata\AdminBundle\Form\Type\ChoiceFieldMaskType;
use Symfony\Component\Form\Extension\Core\Type\TextType;

final class AppMenuAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $formMapper
            ->add('linkType', ChoiceFieldMaskType::class, [
                'choices' => [
                    'uri' => 'uri',
                    'route' => 'route',
                ],
                'map' => [
                    'route' => ['route', 'parameters'],
                    'uri' => ['uri'],
                ],
                'placeholder' => 'Choose an option',
                'required' => false
            ])
            ->add('route', TextType::class)
            ->add('uri', TextType::class)
            ->add('parameters')
        ;
    }
}

map: Associative array. Describes the fields that are displayed for each choice.

Sonata\AdminBundle\Form\Type\AdminType

Setting a field type of Sonata\AdminBundle\Form\Type\AdminType will embed another admin class and use the embedded admin's configuration when editing this field. Sonata\AdminBundle\Form\Type\AdminType fields should only be used when editing a field which represents a relationship between two model classes.

This type allows you to embed a complete form for the related element, which you can configure to allow the creation, editing and (optionally) deletion of related objects.

For example, lets use a similar example to the one for Sonata\AdminBundle\Form\Type\ModelType above. This time, when editing a Page using PageAdmin we want to enable the inline creation (and editing) of new Images instead of selecting an existing Image from a list.

First we need to create an ImageAdmin class and register it as an admin class for managing Image objects. In our services.yaml we have an entry for ImageAdmin that looks like this:

# config/services.yaml

services:
    app.admin.image:
        class: App\Admin\ImageAdmin
        arguments:
            - ~
            - App\Entity\Image
            - 'Sonata\AdminBundle\Controller\CRUDController'
        calls:
            - [setTranslationDomain, ['App']]
        tags:
            - { name: sonata.admin, manager_type: orm, label: 'Image' }

To embed ImageAdmin within PageAdmin we need to change the reference for the image1 field to AdminType in our PageAdmin class:

// src/Admin/PageAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use Sonata\AdminBundle\Form\Type\AdminType;

final class PageAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $formMapper
            ->add('image1', AdminType::class)
        ;
    }
}

We do not need to define any options since Sonata calculates that the linked class is of type Image and the service definition (in services.yaml) defines that Image objects are managed by the ImageAdmin class.

The available options (which can be passed as a third parameter to FormMapper::add()) are:

delete: defaults to true and indicates that a 'delete' checkbox should be shown allowing the user to delete the linked object.
btn_add, btn_list, btn_delete and btn_catalogue:: The labels on the add, list and delete buttons can be customized with these parameters. Setting any of them to false will hide the corresponding button. You can also specify a custom translation catalogue for these labels, which defaults to SonataAdminBundle.

Sonata\Form\Type\CollectionType

The Sonata\Form\Type\CollectionType is meant to handle creation and editing of model collections. Rows can be added and deleted, and your model abstraction layer may allow you to edit fields inline. You can use type_options to pass values to the underlying forms:

// src/Admin/ProductAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use Sonata\Form\Type\CollectionType;
use Symfony\Component\Form\Extension\Core\Type\HiddenType;

final class ProductAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $formMapper
            ->add('sales', CollectionType::class, [
                'type_options' => [
                    // Prevents the "Delete" option from being displayed
                    'delete' => false,
                    'delete_options' => [
                        // You may otherwise choose to put the field but hide it
                        'type'         => HiddenType::class,
                        // In that case, you need to fill in the options as well
                        'type_options' => [
                            'mapped'   => false,
                            'required' => false,
                        ]
                    ]
                ]
            ], [
                'edit' => 'inline',
                'inline' => 'table',
                'sortable' => 'position',
            ])
        ;
    }
}

The available options (which can be passed as a third parameter to FormMapper::add()) are:

btn_add and btn_catalogue:: The label on the add button can be customized with this parameters. Setting it to false will hide the corresponding button. You can also specify a custom translation catalogue for this label, which defaults to SonataAdminBundle.

Tip

A jQuery event is fired after a row has been added (sonata-admin-append-form-element). You can listen to this event to trigger custom JavaScript (eg: add a calendar widget to a newly added date field)

Tip

Setting the 'required' option to true does not cause a requirement of 'at least one' child entity. Setting the 'required' option to false causes all nested form fields to become not required as well.

Tip

You can check / uncheck a range of checkboxes by clicking a first one, then a second one with shift + click.

Sonata\AdminBundle\Form\Type\CollectionType

This bundle handle the native Symfony collection form type by adding:

an add button if you set the allow_add option to true.
a delete button if you set the allow_delete option to true.

Tip

A jQuery event is fired after a row has been added (sonata-admin-append-form-element). You can listen to this event to trigger custom JavaScript (eg: add a calendar widget to a newly added date field)

Tip

A jQuery event is fired after a row has been added (sonata-collection-item-added) or before deleted (sonata-collection-item-deleted). A jQuery event is fired after a row has been deleted successfully (sonata-collection-item-deleted-successful) You can listen to these events to trigger custom JavaScript.

FieldDescription options

The fourth parameter to FormMapper::add() allows you to pass in FieldDescription options as an array. The most useful of these is admin_code, which allows you to specify which admin to use for managing this relationship. It is most useful for inline editing in conjunction with the Sonata\AdminBundle\Form\Type\AdminType form type.

The value used should be the admin service name, not the class name. If you do not specify an admin_code in this way, the default admin class for the field's model type will be used.

For example, to specify the use of the admin class which is registered as sonata.admin.imageSpecial for managing the image1 field from our PageAdmin example above:

// src/Admin/PageAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use Sonata\AdminBundle\Form\Type\AdminType;

final class PageAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $formMapper
            ->add('image1', AdminType::class, [], [
                'admin_code' => 'sonata.admin.imageSpecial'
            ])
        ;
    }
}

Other specific field configuration options are detailed in the related abstraction layer documentation.

Adding a FormBuilderInterface

You can add Symfony FormBuilderInterface instances to the FormMapper. This allows you to re-use a model form type. When adding a field using a FormBuilderInterface, the type is guessed.

Given you have a PostType like this:

// src/Form/PostType.php

use Symfony\Component\Form\FormBuilderInterface;
use Symfony\Bridge\Doctrine\Form\Type\EntityType;
use Symfony\Component\Form\Extension\Core\Type\TextType;
use Symfony\Component\Form\Extension\Core\Type\TextareaType;
use Symfony\Component\Form\AbstractType;

class PostType extends AbstractType
{
    public function buildForm(FormBuilderInterface $builder, array $options)
    {
        $builder
            ->add('author', EntityType::class, [
                'class' => User::class
            ])
            ->add('title', TextType::class)
            ->add('body', TextareaType::class)
        ;
    }
}

you can reuse it like this:

// src/Admin/Post.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;
use App\Form\PostType;

final class Post extend AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $builder = $formMapper->getFormBuilder()->getFormFactory()->createBuilder(PostType::class);

        $formMapper
            ->with('Post')
                ->add($builder->get('title'))
                ->add($builder->get('body'))
            ->end()
            ->with('Author')
                ->add($builder->get('author'))
            ->end()
        ;
    }
}

Types options

General

label: You can set the label option to false if you don't want to show it:

// src/Admin/PageAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Sonata\AdminBundle\Admin\AbstractAdmin;

final class PageAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $formMapper
            ->add('status', null, [
                'label' => false
            ])
        ;
    }
}

Symfony\Component\Form\Extension\Core\Type\ChoiceType

sortable: This option can be added for multiple choice widget to activate select2 sortable:

// src/Admin/PageAdmin.php

use Sonata\AdminBundle\Form\FormMapper;
use Symfony\Component\Form\Extension\Core\Type\ChoiceType;
use Sonata\AdminBundle\Admin\AbstractAdmin;

final class PageAdmin extends AbstractAdmin
{
    protected function configureFormFields(FormMapper $formMapper)
    {
        $formMapper
            ->add('multiChoices', ChoiceType::class, [
                'multiple' => true,
                'sortable' => true,
            ])
        ;
    }
}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

form_types.rst

form_types.rst

Form Types

Sonata\AdminBundle\Form\Type\ModelType

Sonata\AdminBundle\Form\Type\ModelListType

Sonata\AdminBundle\Form\Type\ModelHiddenType

Sonata\AdminBundle\Form\Type\ModelAutocompleteType

Sonata\AdminBundle\Form\Type\ChoiceFieldMaskType

Sonata\AdminBundle\Form\Type\AdminType

Sonata\Form\Type\CollectionType

Sonata\AdminBundle\Form\Type\CollectionType

FieldDescription options

Adding a FormBuilderInterface

Types options

General

Symfony\Component\Form\Extension\Core\Type\ChoiceType

Files

form_types.rst

Latest commit

History

form_types.rst

File metadata and controls

Form Types

Admin related form types

Sonata\AdminBundle\Form\Type\ModelType

Sonata\AdminBundle\Form\Type\ModelListType

Sonata\AdminBundle\Form\Type\ModelHiddenType

Sonata\AdminBundle\Form\Type\ModelAutocompleteType

Sonata\AdminBundle\Form\Type\ChoiceFieldMaskType

Sonata\AdminBundle\Form\Type\AdminType

Sonata\Form\Type\CollectionType

Sonata\AdminBundle\Form\Type\CollectionType

FieldDescription options

Adding a FormBuilderInterface

Types options

General

Symfony\Component\Form\Extension\Core\Type\ChoiceType