New to Telerik UI for Blazor? Download free 30-day trial

Conditionally Hide Hierarchical Grid Expand Button


Product Grid for Blazor


How would you remove the icon to expand a detail Grid only for certain rows? Some rows will not have detail data and should not be expandable.

I would like the expand to only be visible when it has further data to expand.


Use the OnRowRender event to evaluate the current row item (for example, whether it has child items in a collection or some other flag your application has).

Then, if you want to hide the expand icon, set a CSS class to the row that will hide the icon in the expand cell. It is also important to disable the pointer events of the cells with no expand icons, so the user cannot click them to open the empty child Grid even though the plus icon is hidden.

Hide the expand button conditionally per row

@* Use CSS and the RowRender event to hide the detail template expand button conditionally *@
        A CSS rule that matches the OnRowRender handler to 
        conditionally hide hierarchy expand buttons and 
        stops the pointer events of the cells with no
        expand buttons.
        You may want to add this to your site-wide stylesheet.
    .k-grid td.k-hierarchy-cell * {
        display: none;

    .k-grid td.k-hierarchy-cell {
        pointer-events: none;

<TelerikGrid Data="@salesTeamMembers" OnRowRender="@OnRowRenderHandler">
            var employee = context as MainModel;
            <TelerikGrid Data="@employee.Orders" Pageable="true" PageSize="5">
                    <GridColumn Field="OrderId"></GridColumn>
                    <GridColumn Field="DealSize"></GridColumn>
        <GridColumn Field="Id"></GridColumn>
        <GridColumn Field="Name"></GridColumn>

@code {
    // conditionally hide the hierarchy expand button
    void OnRowRenderHandler(GridRowRenderEventArgs args)
        MainModel item = args.Item as MainModel;

        bool hasNoHierarchy = item.Orders == null || item.Orders.Count == 0;
        args.Class = hasNoHierarchy ? "no-children" : "";

    // sample data generation follows
    List<MainModel> salesTeamMembers { get; set; }

    protected override void OnInitialized()
        salesTeamMembers = GenerateData();

    private List<MainModel> GenerateData()
        List<MainModel> data = new List<MainModel>();
        for (int i = 0; i < 5; i++)
            MainModel mdl = new MainModel { Id = i, Name = $"Name {i}" };

            // we add hierarchy data only to some rows
            // we will hide the expand button for the rest
            if (i % 3 == 0)
                mdl.Orders = Enumerable.Range(1, 15).Select(x => new DetailsModel { OrderId = x, DealSize = x ^ i }).ToList();
        return data;

    public class MainModel
        public int Id { get; set; }
        public string Name { get; set; }
        public List<DetailsModel> Orders { get; set; }

    public class DetailsModel
        public int OrderId { get; set; }
        public double DealSize { get; set; }


If you have hierarchical data, especially data that goes many levels deep, you may want to consider the TreeList component instead of a grid. It can also load data on demand.

You may also want to load data on demand for the detail template instead of loading it all at once initially, you can see one easy way to do that in the following sample project: Load data on demand in a Hierarchy Grid.

In this article