To whom it may concern,

       I’m one of your subscribed customers. And I’m writing to seek help in order to realize a filter display I want KendoGrid to show.

The following screenshot is the date filter display that KendoGrid has:

Can it be changed to the similar way as the following picture shows?

It is also acceptable if the filter can provide 3 different options to easily choose from for users:

1. Before a certain date that the user can choose from a calendar just like the picture above
2. After a certain date
3. Between two dates
4. In a certain date 

Thanks.

Best Regards,

BLACK STREAM

Hello,

since I updated Telerik UI for ASP.net MVC from version 2019.1.220 to 2019.2.514, the paging part of the grid doesn't display as expected in IE11 with compatibility with IE9  (<meta http-equiv="x-ua-compatible" content="IE=9">)

If I remove the compatibility with IE9, it's ok, but I need it to support older computer.  

version 2019.1.220: 

version 2019.2.514:

 Is there a solution to display it correctly?

Thank you very much and best regards.

Emmanuel Tharin

When the page first loads, everything looks okay...

But if I show a hidden column...

Here's what happens...

The newly shown column is circled in blue. The problem, as you can see, is that the position of the column circled in red should actually be swapped with the column to the left of it. And column #2 (ordering from left to right in the picture, starting from #1) now has an incorrect parent header ("Average") - it should be "Total". And column #4 (the one circled in red), "Constrained", should have a parent header of "Average" (that gray one in column #2).

And just FYI, if I show another column (which should also be under "Session Time [minutes]")...

...then here's what we get...

(Newly shown column circled in blue.)

But, you can see that the data columns are placed correctly. Just not the headers.

The issue is present only when a field in the model has been updated. When an invalid value is attempted to be saved, the validation is triggered. Upon pressing the Esc key, the dirty indicator should not be shown.

The expected behavior would be to not show the dirty indicator at all as the value has been returned to the initial one. Furthermore, the indicator is not positioned in the left top corner but immediately above the value.

Steps to replicate:

1. Change the value of any field.

2. Navigate to a field which has validation.

3. Set an invalid value in order to trigger the validation, respectively show a validation message.

4. Press Esc to undo the change.

5. The dirty indicator is shown and mispositioned.

Dojo sample:

https://dojo.telerik.com/iHoRaWIg

Short video demonstration:

https://screencast-o-matic.com/watch/cqhbjKTeK2

Hi Viktor,

We are looking for functionality of Context Menu on Columns of Kendo MVC grid.

We want various column selection on grid header.

Please help us to get this feature.

Regards

Supriya

Unless I am missing it somehow, I do not think the Grid control ( I was specifically using the MVC Grid control) does not support

1. A search feature that searches all rows and columns for the supplied text.  I know you can use the filter at the top of each column to search just that column but looking for ability to search the entire dataset.

 2.  Ability to set the column widths as a percentage of the total space available.  It looks to me like it only allows a specific px setting.

These would be good adds.  If either of these are currently possible and I missed it somehow, would appreciate response regarding how to achieve this.

Thanks,

David. 

JWT Token authentication has become very popular and one of the main tools to provide authorization and authentication.
JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. In authentication, when the user successfully logs in using their credentials, a JSON Web Token will be returned. 

Whenever the user wants to access a protected route or resource, the user agent should send the JWT, typically in the Authorization header using the Bearer schema. This can be, in certain cases, a stateless authorization mechanism. The server's protected routes will check for a valid JWT in the Authorization header, and if it's present, the user will be allowed to access protected resources. If the JWT contains the necessary data, the need to query the database for certain operations may be reduced, though this may not always be the case.

It would be really helpful to have a built in functionaly ".Authorization(token)" that adds an authorization header to all the requests made by the grid.