Hi,
`GridCellsSettings.group.groupHeader` only works when set in <Grid />, doesn't work if set in <Column />.
This works:
<Grid
cells={{
group: { groupHeader: GroupMyHeaderCustomCell }
}}
>
This doesn't work:
<Grid>
<Column
cells={{
group: { groupHeader: GroupMyHeaderCustomCell }
}}
/>
</Grid>Can you please explain the difference?
Thanks,
Jie

Hi All,
I'm Kamal Hinduja, was born in Chennai (India) and now resides in Geneva, Switzerland(Swiss). Can anybody explain how to apply a custom
theme to all Kendo React components?
Thanks, Regards
Kamal Hinduja Geneva, Switzerland

Title: How to Restrict Checkbox Selection to Only Checkbox Click in Kendo Grid Row Selection?
Description:
I am using the Kendo React Data Grid with row selection enabled via a checkbox column. My goal is to select a row only when the checkbox itself is clicked, not when any other part of the row is clicked.
However, currently, when I click anywhere in the row (e.g., the staff name), the checkbox also gets selected. This creates a problem in my use case — clicking the staff name navigates to the staff profile, but it also toggles the checkbox, which is unintended.
I want the checkbox to be selected only when the checkbox is clicked, and not when clicking anywhere else in the row.
I am using
but the issue still occurs.
I have a custom cell rendering for the name column that navigates on click.
How can I configure the Kendo Grid so that:
Checkbox selection is triggered only by clicking the checkbox.
Clicking on any other cell (especially with navigation) does not toggle checkbox selection?
Thanks in advance!
Hi Kendo Team,
I'm currently working with the KendoReact Gantt Chart and would like to customize how many dates are visible in the chart for different views (Yearly, Monthly, Weekly). Specifically, I want to control the time span shown for each view — for example:
In Yearly view, show 5 years instead of the default range
In Monthly view, limit the chart to show only 6 months at a time
In Weekly view, show just 4 weeks of data
Is there a recommended way to configure the visible date range or scale for each view mode?
Any guidance or code example would be greatly appreciated!
Thanks
We are trying to activate the Kendo UI license as part of our CI/CD pipeline but are facing issues executing the npx kendo-ui-license activate command in our environment.
We are using Microsoft OneBranch CI/CD pipeline templates.
Our NPM dependencies (including @progress packages) are hosted in a private Azure Artifacts registry.
When we attempt to run the following command in the pipeline:
we receive the following error:
This appears to be due to the agent’s inability to establish a secure connection to the required endpoint(s), possibly related to Telerik's license validation server.
Could you please guide us on how to properly activate the Kendo UI license in a CI/CD environment that cannot execute the above command due to network restrictions?
Is there a supported method to pre-activate the license locally and provide the license file (e.g., .kendo-ui-license.json) in the pipeline instead?
If so, could you confirm whether copying the license file to the appropriate location (e.g., ~/.kendo-ui-license.json) is sufficient for the build to proceed without executing the activation command?
We would appreciate your assistance in identifying a secure and compliant way to use our licensed packages in our automated build process.
Thank you,
Milin Hapani

Hi all,
I've been working with Kendo Form for a while and I'm now trying to add some custom behavior or styling to all my form fields. For example, I might want to consistently wrap them with extra logic, validation hints, or a custom layout.
Here’s a simplified case using a `Checkbox`:
<Field component={Checkbox} name="acceptTerms" />To achieve the desired behavior, I’ve tried creating a `MyCustomCheckbox` component (see here). That works fine — but I don’t want to have to create `MyCustomInput`, `MyCustomDropdown`, `MyCustomDatePicker`, etc. for every component I use.
Is there a way to apply the same wrapper or logic at a more general level, so that I can just write:
<Field component={Input} name="email" />
<Field component={Checkbox} name="acceptTerms" />…and have both get wrapped or enhanced in the same way — without duplicating the logic in multiple custom components?
Any tips or patterns would be greatly appreciated!
Thanks,
Grant
