The ability to export a grid to excel has been a great addition, we would like the ability to export in CSV and XML also.

Add support for hidden fields. There could be an alternative way of adding them to the Items collection, e.g.

.AddHidden()

Consider the cases when the hidden field is bound to a model field and when it isn't bound to the model. The latter could be a scenario involving antiForgeryTokens: 

<input type="hidden" name="__RequestVerificationToken" value="token" />

In both cases you should be able to set the value of the hidden field programmatically and submit it with the form.

I'm currently evaluating the ASP .Net Core Components and whilst I'm liking it so far, I have to say - the documentation leaves a lot to be desired.

At the moment, I am trying to use grid and looking at documentation, I have no idea if I am meant to be looking in Kendo.Mvc.UI.Fluent or Kendo.Mvc.UI - and when I am there and find an item, there just isn't enough detail. In addition, the demos section appears to actually be more helpful and I'm constantly looking there.

What caused me to write this is that I have simply enabled GridFilterMode.Row on an instance and whilst I like it, I want to change the default from "Is Equal To" to "Contains"... I have been experimenting for the past few hours without any luck and I'm going round in circles on documentation:

I can see that Filterable requires GridFilterMode, but the documentation is lacking - https://docs.telerik.com/aspnet-core/api/Kendo.Mvc.UI/GridFilterMode#kendomvcuigridfiltermode

I then try to find the filterable modes documentation, but, half the features/methods just don't seem to have any affect whatsoever.

Personally, I'm having great luck learning about your components from the demo section and adapting the code to suite my needs - but, if there isn't a demo, it appears to be a very hard task to learn what is and isn't possible.

Implement Recurrence Rule Parser helper that uses the Scheduler recurrenceRule string and parses it in a usable format on the server.

There is already a similar helper for Telerik UI for ASP.NET Ajax.

Per the documentation for the Grid's Search Panel:

"When the server operations are enabled, you can search only by using string fields."

This is an oddly-specific limitation to have that causes an awkward user experience. Grids in some areas with limited data might use client operations and, as a result, the Search Panel is capable of searching all columns in a Grid. Other areas, however, might have grids with significantly more data and be using server operations for performance reasons. A side-effect of this would mean the Search Panel is incapable of filtering on non-string fields. This not only might lead to unexpected results to an end-user, but also requires the developer to explicitly list each string field that can be searched. If a developer forgets to list only string fields, the default action will be for it to attempt to filter on all fields. If any fields happen to not be strings, you still get a loading indicator as if it's attempting to filter, but the Ajax request silently fails and returns an error 500 behind the scenes.

There are some manual workarounds discussed here, as well as some information as to why this limitation exists. It seems like the problems causing these limitations are known, as are some rough workarounds to get around it. It would be great if we could get some official support to address this limitation so developers aren't left to either work around it on their own or avoid using this feature altogether. This feature would be great if it weren't for this limitation. A single place to quickly and easily type in something to filter on, and have that filter applied against all columns could definitely save some time and be very useful, but with this limitation with a pretty technical explanation (from an end-user perspective), the unexpected mixed results could instead lead to confusion and frustration, and distrust of this feature.

Due to changes in the ASP.NET Core framework and how the Authentication is implemented the MVC5 implementation of the SecurityTrimming option became obsolete. 

1. Allow the elastic behavior of the PDFViewer's mobile scroller to be disabled. Currently, when scrolling to the top or to the bottom, the document jumps and then immediately re-adjusts its position under the widget's header/bottom border.

2. Add the ability to manually scroll the document up/down with mousedown.

3. Add keyboard scrolling support.

Having a floating label functionality similar to the one available for the native Vue DropDownList, would be nice to have.

https://www.telerik.com/kendo-vue-ui/components/dropdowns/floating-labels/

Currently, the functionality for creating a toolbar template with TagHelpers is not available. 

We have the need to create a chart to display Risk Information. Below is the image of a risk matrix as defined on pages 96 in AFPAM63-128 https://static.e-publishing.af.mil/production/1/saf_aq/publication/afpam63-128/afpam63-128.pdf -- there are more examples on page 101

Another example of a risk matrix can be seen on page 18 here -> https://static.e-publishing.af.mil/production/1/af_se/publication/afi90-802/afi90-802.pdf

I've copied the images here for convenience.

Would it be possible to add this to the Kendo Chart backlog?

Feature request

Add Refresh method to the ASP.NET Core Timeline wrapper.  It should allow user to reload the component using the current data items.

Hi, Any plan to release asp.core with angular 2 template like mvc5 with angular . 

I am looking for an extension to the Grid Columns fluent api that adds .Exportable(true or false).  Exportable(true) would be the default and indicate that this column does get exported when exporting to Excel (or PDF).  Exportable(false) would indicate that the column does NOT get exported.

Imagine the following Grid Definition:

@(Html.Kendo().Grid<Services>
    ()
    .Name("gridMain")
    .Columns(columns =>
    {
        columns.Bound(p => p.ServiceId).ClientTemplateId("rowNumTemplate").Title("Row").Width(50);
        //columns.Bound(p => p.ServiceId).ClientTemplateId("cmdsTemplate").Title("Cmds").Width(125).Media("(min-width: 768px)");
        columns.Bound(p => p.ServiceCode).Media("(min-width: 768px)");
        columns.Bound(p => p.ServiceId).ClientTemplateId("xsTemplate").Title("Service / Desc / Code").Media("(max-width: 768px)");
        columns.Bound(p => p.ServiceId).ClientTemplateId("serviceTemplate").Title("Service / Desc").Media("(max-width: 992px) and (min-width: 768px)");
        columns.Bound(p => p.ServiceName).Media("(min-width: 992px)");
        columns.Bound(p => p.ServiceDescription).Media("(min-width: 992px)");
        columns.Bound(p => p.ServiceActive).ClientTemplateId("activeTemplate").Width(60).Media("(min-width: 768px)");
        columns.Bound(p => p.ServiceId).ClientTemplateId("btnsTemplate").Title("View/Edit/Del").Width(150);
        //columns.Bound(p => p.ServiceId).ClientTemplateId("xsCmdsTemplate").Title("Cmds").Media("(max-width: 768px)");
    })
    .Scrollable(scrollable => scrollable.Endless(true))
    .Pageable(p => p.Numeric(false).PreviousNext(false))
    .ToolBar(t => t.Search())
    .Search(s => { s.Field(c => c.ServiceCode); s.Field(c => c.ServiceName); s.Field(c => c.ServiceDescription); })
    .Resizable(resize => resize.Columns(true))
	.ToolBar(t => t.Excel().Text("Excel"))
    .Excel(excel => excel
		.FileName("ABT_Services.xlsx")
		.Filterable(true)
	)
    .DataSource(dataSource =>
    dataSource
    .WebApi()
    .PageSize(Model.GridPageSize)
    .Model(model =>
    {
        model.Id(p => p.ServiceId);
    })
    .Events(events => events.Error("errorHandler").RequestEnd("gridMainRequestEnd"))
    .Read(read => read.Action("Get", "Services"))
    )
)

What I would like to do is define a column like the following:

        columns.Bound(p => p.ServiceId).ClientTemplateId("rowNumTemplate").Title("Row").Width(50).Exportable(false);

In the case above, the "Row" column would not be Exported to Excel.

If you take a closer look at the Columns definition above you will see that the configuration is implemented to support responsive page sizing.  Because the current implementation of Export to Excel does not allow an Exportable(true/false), I get these columns that I don't want in the exported Excel.

Although there appear to be workarounds (like keeping a second hidden grid -- a poor solution at best), none would be as useful to a Developer as defining an Exportable(true/false) as part of the Column configuration.

Thanks for considering my request.

Provide built-in integration of RadioButton / RadioGroup in the Form

We are building our product using an ASP.NET Core MVC project and are very excited to use the Kendo UI Sass Template.  We took a lot of time to integrate the Bootstrap Sass distribution into the project build process using Gulp and Node.js in Visual Studio to build and minify the Bootstrap Sass files so we have full control over the style and features included in our CSS files to maximize performance.

Part of this process was to make sure we used the same exact process used by Bootstrap to compile the Sass into the CSS so our process did not introduce bugs because the Sass was compiled and minified using different options than the Bootstrap team.

It would be greate if you could include options in the new project wizard to include the Kendo UI Sass template and the code necessary to build the CSS.  Additionally it would be ideal if your Sass  can be compiled and minified using the same options as Bootstrap so that if a team decides to combine and minify that code it will still work as expected.

A bonus would be if you allowed the template to also select to use Bootstrap Sass alongside the Kendo UI Sass so that a project like this can be setup quickly with minimal effort on the developers part.

Thanks for taking this into consideration,

Bryan

kendo.aspnetmvc.js does not account for server aggregates serialized with came case property names like it does for Groups.

Can the following code (minus the comments) be included in a future release to resolve this?

function translateAggregateResults(aggregate) {
            var obj = {};
            // LSS: support for camel case serialization
            obj[(aggregate.AggregateMethodName || aggregate.aggregateMethodName).toLowerCase()] = (aggregate.Value || aggregate.value);
            return obj;
        }
        function translateAggregate(aggregates) {
            var functionResult = {}, key, functionName, aggregate;
            for (key in aggregates) {
                functionResult = {};
                aggregate = aggregates[key];
                for (functionName in aggregate) {
                    functionResult[functionName.toLowerCase()] = aggregate[functionName];
                }
                aggregates[key] = functionResult;
            }
            return aggregates;
        }
        function convertAggregates(aggregates) {
            var idx, length, aggregate;
            var result = {};
            for (idx = 0, length = aggregates.length; idx < length; idx++) {
                aggregate = aggregates[idx];
                // LSS: support for camel case serialization
                result[(aggregate.Member || aggregate.member)] = extend(true, result[(aggregate.Member || aggregate.member)], translateAggregateResults(aggregate));
            }
            return result;
        }
        extend(true, kendo.data, {
            schemas: {
                'aspnetmvc-ajax': {
                    groups: function (data) {
                        return $.map(this._dataAccessFunction(data), translateGroup);
                    },
                    aggregates: function (data) {
                        data = data.d || data;
                        // LSS: support for camel case serialization
                        var aggregates = data.AggregateResults || data.aggregateResults || [];
                        if (!$.isArray(aggregates)) {
                            for (var key in aggregates) {
                                aggregates[key] = convertAggregates(aggregates[key]);
                            }
                            return aggregates;
                        }
                        return convertAggregates(aggregates);
                    }
                }
            }
        });

Hi.

In Kendo UI for ASP.NET MVC, I'm able to import the following file types into the Editor:

Docx

Rtf

Html

Plain Text

I'm also able to export to the following file types:

Docx

Rtf

Pdf

Html

Plain Text

I expected this functionality to also exist in the Editor control in Kendo UI for ASP.NET Core.

This functionality seems to be missing from Kendo UI for ASP.NET Core.

Related post: https://www.telerik.com/forums/export-to-rtf-or-docx

Thank you.