Creating your first grid
In order to use grids, you need to register your entity as a Sylius resource. Let us assume you have a Supplier model in your application, which represents a supplier of goods in your shop and has several fields, including name, description and enabled.
In order to make it a Sylius resource, you need to add the AsResource
attribute and implement ResourceInterface
.
namespace App\Entity;
use Sylius\Resource\Metadata\AsResource;
use Sylius\Resource\Model\ResourceInterface;
#[AsResource]
class Supplier implements ResourceInterface
{
// ...
}
That's it! Your class is now a resource. In order to learn what it means, please refer to the SyliusResourceBundle documentation.
Grid Maker
You can create your grid using the Symfony Maker bundle.
$ bin/console make:grid
Grid Definition
Now we can configure our first grid:
sylius_grid:
grids:
app_admin_supplier:
driver:
name: doctrine/orm
options:
class: App\Entity\Supplier
fields:
name:
type: string
label: app.ui.name
enabled:
type: twig
label: app.ui.enabled
options:
template: '@SyliusBootstrapAdminUi/shared/grid/field/boolean.html.twig' # This will be a checkbox field
Using your grid on an index operation
The SyliusResourceBundle
allows you to use a grid into an index operation:
namespace App\Entity;
use App\Grid\AdminSupplierGrid;
use Sylius\Resource\Metadata\AsResource;
use Sylius\Resource\Metadata\Index;
use Sylius\Resource\Model\ResourceInterface;
#[AsResource(
section: 'admin', // This will influence the route name
routePrefix: '/admin',
templatesDir: '@SyliusAdminUi/crud', // This directory contains the generic template for your list
operations: [
// You can use either the FQCN of your grid
new Index(grid: AdminSupplierGrid::class)
// Or you can use the grid name
new Index(grid: 'app_admin_supplier')
],
)]
class Supplier implements ResourceInterface
{
// ...
}
This will generate the following path:
------------------------------ ---------------------------
Name Path
------------------------------ ---------------------------
app_admin_supplier_index /admin/suppliers
Now, your new grid should look like this when accessing the index on /admin/suppliers/:

Defining Filters
To allow users to search for specific items in the grid, you can use filters.
sylius_grid:
grids:
app_admin_supplier:
# ...
filters:
name:
type: string
label: Name
enabled:
type: boolean
label: Enabled
How will it look like in the admin panel?

What about filtering by fields of related entities? For instance if you would like to filter your suppliers by their country of origin, which is a property of the associated address entity.
This first requires a custom repository method for your grid query:
sylius_grid:
grids:
app_admin_supplier:
driver:
name: doctrine/orm
options:
class: App\Entity\Supplier
repository:
method: mySupplierGridQuery
Note
The repository method must return a queryBuilder object, as the query needs to adjust based on the filters and sorting the user will apply later.
Furthermore, all sub entities you wish to use later on for filtering must be joined explicitly in the query.
Then you can set up your filter accordingly:
sylius_grid:
grids:
app_admin_supplier:
# ...
filters:
# ...
country:
type: string
label: origin
options:
fields: [address.country]
form_options:
type: contains
Default Sorting
You can define by which field you want the grid to be sorted and how.
sylius_grid:
grids:
app_admin_supplier:
# ...
sorting:
name: asc
# ...
Then in the fields section, indicate that the field can be used for sorting:
sylius_grid:
grids:
app_admin_supplier:
# ...
fields:
name:
type: string
label: sylius.ui.name
sortable: ~
# ...
If your field is not of a "simple" type, e.g. a twig template with a specific path, you can enable sorting with the following definition:
sylius_grid:
grids:
app_admin_supplier:
# ...
fields:
# ...
origin:
type: twig
options:
template: "@App/Grid/Fields/myCountryFlags.html.twig"
path: address.country
label: app.ui.country
sortable: address.country
# ...
Pagination
You can limit how many items are visible on each page by providing an array of integers into the limits
parameter. The first element of the array will be treated as the default, so by configuring:
sylius_grid:
grids:
app_admin_supplier:
# ...
limits: [30, 12, 48]
# ...
you will see thirty suppliers per page, also you will have the possibility to change the number of elements to either 12 or 48.
Note
Pagination limits are set by default to 10, 25 and 50 items per page. In order to turn it off, configure limits: ~.
Actions Configuration
Next step is adding some actions to the grid: create, update and delete.
First, we need to create these operations on our resource:
namespace App\Entity;
use App\Grid\AdminSupplierGrid;
use Sylius\Resource\Metadata\AsResource;
use Sylius\Resource\Metadata\Create;
use Sylius\Resource\Metadata\Delete;
use Sylius\Resource\Metadata\Index;
use Sylius\Resource\Metadata\Update;
use Sylius\Resource\Model\ResourceInterface;
#[AsResource(
// ...
operations: [
new Create(),
new Update(),
new Delete(),
// ...
],
)]
class Supplier implements ResourceInterface
{
// ...
}
These new operations are now available:
------------------------------ -----------------------------
Name Path
------------------------------ -----------------------------
app_admin_supplier_create /admin/suppliers/new
app_admin_supplier_update /admin/suppliers/{id}/edit
app_admin_supplier_delete /admin/suppliers/{id}/delete
app_admin_supplier_index /admin/suppliers
Then we need to add these operations into our Grid using Actions.
Note
There are two types of actions that can be added to a grid: main
which "influence" the whole grid (like adding new objects) and item
which influence one row of the grid (one object) like editing or deleting.
sylius_grid:
grids:
app_admin_supplier:
# ...
actions:
main:
create:
type: create
item:
update:
type: update
delete:
type: delete
This activates such a view on the /admin/suppliers/
path:

Your grid is ready to use!
Last updated
Was this helpful?