Hi, 

I am looking for a solution for locked custom column and I bumped into some example, but seems like it's already outdated and not working anymore at least due to missing 'cell' property in GridColumn component and missing tdProps in GridCellProps interface.

Is there any chance to bring the example up-to-date?
or are there any fresh articles/knowledge-base related to this problem?
example

related post here:
related forum post

Thanks,
Bohdan

We have a strange issue with the newest Grid component. I have this issue recreated here: https://codesandbox.io/p/devbox/proud-forest-v49cp6

The upper most input element is just to trigger state change. To see the issue:

1. Click on Edit in any row in the grid to start inline editing of that row
2. Start typing in the upper most input field (above the grid) 
3. After each letter the Grid will get focus preventing me from writing in the input!!!

Now if I enable editing in two rows at once (two rows are in edit state) this behavior is absent and I can normally type in my input above the grid. What is wrong?

Hi,

If Grid's last column has a long title, trying drag-n-drop to group that last column will get stuck. The mouse cursor's title box is too wide, it overflows to outside of the grid, then the cursor can't be moved anymore.

To reproduce, use this example - https://www.telerik.com/kendo-react-ui/components/grid/grouping, resize the browser to a smaller size so that "Category Name" column title fill up the entire column width. Then try to drag "Category Name" column.

Please see the attached screenshot too.

Thanks,

Jie

Hi Team,

I want to use the `GridToolbarColumnsChooser` in the Grid Toolbar (example) but there isnt any obvious way to customize the selectable visible/columns. In my use case, not all columns can be hidden, but there is no control in this component to do so.

I see there is a GridColumnMenuColumnsChoose, which accepts a single 'column' property, not sure if this is intentional, or maybe this is not what im looking for?

Anyway, any help to be able to customize the list of selectable columns would be helpful.

Thanks,
Grant

I am getting the following WARNINGS

$_default-colors: $kendo-colors

from

node_modules/@progress/kendo-theme-bootstrap/scss/core/_index.scss 23:5 @forward

$_default-elevation: $kendo-elevation,

$_default-font-sizes: $kendo-font-sizes,

I am giving only some examples. Is there a way to fix these warnings.

Please help

Thank you

In KendoReact Grid, when using grouping with multiple hierarchy levels, the Grid automatically adds extra horizontal space inside the <td> elements (indentation for group levels).

Technically this makes sense, because each group level needs visual offset.
However, the problem is that there is no built-in way to control or configure this spacing.

As a result:

• extra empty space appears inside <td> cells

• the Grid content becomes wider than expected

• this breaks layout and design, especially in custom UI / strict design systems

Why doesn’t KendoReact Grid expose any API or configuration to control this indentation / spacing for grouped rows?

Is there:

• an official way to customize or limit this space?

• a recommended approach to override or manage this behavior without breaking Grid internals?

Any guidance or best practices would be appreciated.

Example:

In KendoReact Grid, when using grouping with multiple hierarchy levels, the Grid automatically adds extra horizontal space inside the <td> elements (indentation for group levels).

Technically this makes sense, because each group level needs visual offset.
However, the problem is that there is no built-in way to control or configure this spacing.

As a result:

• extra empty space appears inside <td> cells

• the Grid content becomes wider than expected

• this breaks layout and design, especially in custom UI / strict design systems

Why doesn’t KendoReact Grid expose any API or configuration to control this indentation / spacing for grouped rows?

Is there:

• an official way to customize or limit this space?

• a recommended approach to override or manage this behavior without breaking Grid internals?

Any guidance or best practices would be appreciated.

Example: