1. Installs both extensions ASP.NET Core and MVC without the latest MVC and ASP.Net Core product versions
2. Create an ASP.NET Core project with an older version
3. An Update Available Notification appears for ASP.Net Core
4. Click on the "Update Now" button
5. The Upgrade project wizard is launched
6. Click on "Next" button, then the following error appears:
   
   

Hi Team,

I would like to request to add an Html/Tag Helper for the kendo.ui.icon.  

Thanks!

Currently, when exporting a file from the Spreadsheet that contains named ranges, which refer to invalid or missing references (e.g., "#REF!"), the exported file is corrupted when attempting to open it in Excel:

Is it possible to remove any invalid named ranges before exporting the file to avoid such a warning when opening the file in Excel? Alternatively, rewrite the invalid named ranges in the exported file, so they are ignored by Excel when opening the exported file.

By default, when opening a file with invalid named ranges in Excel, there is no automatic warning to the user.

I'm in the process of rewriting all Kendo components to use CSP compatible templates. I'm looking at https://docs.telerik.com/aspnet-core/html-helpers/template/overview which shows how we'd use TemplateComponentName() for popup editors and that we would need to rewrite everything in the popup editor to use Kendo Template's AddHtml or AddComponent methods.

Original:

<div class="mb-2 row required">
	@Html.LabelFor(model => model.FileName, new { @class = "col-sm-4 col-form-label fw-bold text-sm-end" })
	<div class="col-sm-6">
		@(Html.Kendo().TextBoxFor(model => model.FileName).HtmlAttributes(new { @class = "w-100" }))
	</div>
</div>

<div class="mb-2 row">
	@Html.LabelFor(model => model.FileDescription, new { @class = "col-sm-4 col-form-label fw-bold text-sm-end" })
	<div class="col-sm-6">
		@(Html.Kendo().TextBoxFor(model => model.FileDescription).HtmlAttributes(new { @class = "w-100" }))
	</div>
</div>

Rewritten:

@(Html.Kendo().Template()
	.AddHtml("<div class='mb-2 row required'>")
	.AddHtml(@<text>
		@Html.LabelFor(model => model.FileName, new { @class = "col-sm-4 col-form-label fw-bold text-sm-end" })
	</text>)
	.AddHtml("<div class='col-sm-6'>")
	.AddComponent(c => c.TextBoxFor(model => model.FileName).HtmlAttributes(new { @class = "w-100" }))
	.AddHtml("</div></div>")

	.AddHtml("<div class='mb-2 row'>")
	.AddHtml(@<text>
		@Html.LabelFor(model => model.FileDescription, new { @class = "col-sm-4 col-form-label fw-bold text-sm-end" })
	</text>)
	.AddHtml("<div class='col-sm-6'>")
	.AddComponent(c => c.TextBoxFor(model => model.FileDescription).HtmlAttributes(new { @class = "w-100" }))
	.AddHtml("</div></div>")
)

While this works, this markup seems much harder to read than the original. Could this be made to be simpler? Ideally I'd like to be able to drop my existing mix of html and kendo components in one method and it'd parse through to render the template properly.

### Bug report

When adding a <select> element as a custom tool in the Editor, the dropdown does not open.

### Reproduction of the problem

1) Run the Dojo sample and try to open the dropdown in the toolbar:

https://dojo.telerik.com/VVPUopDw

The same example work as expected with version 2023.1.117.

2) When using version 2024.4.1112, if you remove the "ref-toolbar-tool" attribute from the <div class='k-toolbar-item'> element, the dropdown opens as expected.

### Expected/desired behavior

The <select> element must function correctly when added as a custom tool in the toolbar.

### Workaround

Handle the "click" event of the select and prevent the event bubbling:

<script>
    $(function () {
        const selectElements = $('select[id^="symbolSelect_"]');
        $(selectElements).each(function (index) {
            this.addEventListener("click", clickHandlerSymbolSelect);
        });
    });

    function clickHandlerSymbolSelect(e) {
        e.stopPropagation(); //Prevent event bubbling, so Kendo cannot swallow or cancel the event.
        const sendingElement = e.target;
        sendingElement.showPicker();
        return true;
    }
</script>

### Environment

* **Kendo UI version: 2025.1.227
* **jQuery version: 3.7.1
* **Browser: [all]

### Bug report

When an Editor component in inline mode is set as an editor in an InCell editable Grid, the Grid cell does not enter edit mode on "click". The issue occurs since version 2023.1.314.

### Reproduction of the problem

1) Create an InCell editable Grid.

2) Set an Editor component in inline mode as an editor to a specified Grid column.

3) Try to edit the cell.

4) The cell flashes and does not enter edit mode.

A Dojo sample for reporduction: https://dojo.telerik.com/zQUvDQEq (check out the "ProductName" column)

### Expected/desired behavior

The Grid column that uses Editor component in inline mode must be editable.

### Environment

* **Kendo UI version: since 2023.1.314
* **jQuery version: 3.4.1
* **Browser: [all]

Currently, the Editor's ImageBrowser dataSource only uses the default name, size, and type fields: https://docs.telerik.com/kendo-ui/api/javascript/ui/editor/configuration/imagebrowser.schema.model.fields#imagebrowserschemamodelfields

Additional custom fields coming with the response (sent back to the client by the specified end point) are ignored and are not accessible in the ImageBrowser's dataSource.

I'm using an OData datasource to populate the grid.  To make matters worse, the Autocomplete retrieves data for *all* of the grid columns.  I'd say the default behavior should only retrieve the current column's data and preferably use OData groupby to limit the results to distinct values.

Interestingly, the CheckBoxList filter *is* populated from the current grid data, behaving as expected.  

My page is attached and the issue is occurring in the detail grid where Server Filtering is disabled.

Currently, the DatePicker can be set to read-only mode by adding the "readonly" attribute through the HtmlAttributes() option or by calling the client-side readonly() method.

Is it possible to implement a built-in Readonly() option, so the DatePicker is initialized as read-only? For example:

@(Html.Kendo().DatePickerFor(m => m.StratDate)
  .Readonly(true)
)

I am seeing that once a grid checkboxlist column filter exceeds about 1000 items the wait time appears to increase non-linearly (performance is worse than linear.)  For example, with 3,000 items the page freezes for about 30 seconds.  The data is fetched in under 50 milliseconds, so the vast majority of this time appears to be processing by Kendo.

Please see the attached for my configuration.

As a result of an EF Core issue, the ToDataSourceResult() is not able to perform the query when the DataSourceRequest object contains grouping.

The problem occurs using the query below, assembled by Telerik routine:

var temp = _db.Pessoa
    .OrderBy(item => item.Email)
    .Skip(0)
    .Take(40)
    .GroupBy(item => item.Email)
    .OrderBy(g => g.Key)
    .Select(g => new AggregateFunctionsGroup
    {
        Key = g.Key,
        ItemCount = g.Count(),
        HasSubgroups = false,
        Member = "Email",
        AggregateFunctionsProjection = new
        {
            Count_Referencia = _db.Pessoa
                    .Select(t => new
                    {
                        t.IdPessoa,
                        t.Referencia,
                        t.Nome_RazaoSocial,
                        t.Apelido_Fantasia,
                        t.CPF_CNPJ,
                        t.RG_IE,
                        t.Email
                    })
                    .OrderBy(item => item.Email)
                    .Where(item => item.Email == g.Key)
                    .Count()
        },
        Items = g
    })
    .ToList();

In the routine where the AggregateFunctionsGroup is created, the Items property must not only be the query itself, but also the fields specified in the main Select. Or, the call to the Select() method must simply be added:

var temp = _db.Pessoa
    .OrderBy(item => item.Email)
    .Skip(0)
    .Take(40)
    .GroupBy(item => item.Email)
    .OrderBy(g => g.Key)
    .Select(g => new AggregateFunctionsGroup
    {
        Key = g.Key,
        ItemCount = g.Count(),
        HasSubgroups = false,
        Member = "Email",
        AggregateFunctionsProjection = new
        {
            Count_Referencia = _db.Pessoa
                    .Select(t => new
                    {
                        t.IdPessoa,
                        ...
                    })
                    .OrderBy(item => item.Email)
                    .Where(item => item.Email == g.Key)
                    .Count()
        },
        Items = g.Select(t => new
        {
            t.IdPessoa,
            ...
        })
    })
    .ToList();

This way, the issue does not occur.

The grid must allow changes to be made in specific cells, without those changes being committed/saved unless the user clicks on the "Save" button in the toolbar. Basically the users enter in some values for editable currency columns that aren't locked, and (without saving) some columns (both locked and not locked) that are not editable must be refreshed as the value in those cells depend on the edited column. Those cells have client templates and client footer templates which need to be used by whatever is refreshing their cells.

Having this functionality provided built-in will be a nice addition:
https://docs.telerik.com/kendo-ui/knowledge-base/grid-update-particular-row-without-refresh

### Bug report

When opening the filter menu of a specified column through the classic ColumnMenu, the filter container is displayed with scrollbars when the dropdown of the filter operator is opened.

### Reproduction of the problem

1) Define a Grid and enable its classic ColumnMenu.

2) Open the filter menu of a specified column and then open the dropdown to select a filter operator.

3) The filter container has scrollbars. The "k-menu-popup" element has "overflow: auto";

Use the following demo to test the case and select the "classic" type for the ColumnMenu: https://demos.telerik.com/kendo-ui/grid/column-menu

The issue does not appear when using version 2024.4.1112.

### Expected/desired behavior

The filter menu container must not change its appearance when the dropdown opens.

### Workaround:

<style>
.k-menu-popup {
    overflow: visible !important;
}
</style>