Apologies if this has been asked before...

I have a grid where we display a matrix with checkboxes that users can click to check/uncheck items. As long as there aren't  ~ > 1000 rows and columns everything is fine. I turned on virtual scrolling like this:

scrollable: { virtual: true }

and like this:

scrollable: { virtual: "rows, columns" }

neither seems to do much when you have 2500 columns and 3000 rows.

Is this even doable? Is there an example of this somewhere I could see?

Matt

Hello. I have a very weird issue with Kendo grid. After creating a new record the grid seems to firing a destroy event for some random records. it calls DELETE action on the server that modifies some rows in DB:(sets IsActive field to false, updates ModifyDate and some more rows). I am certain that the delete action is called because of these rows are updated as it is configured in the action. the rows that are being deleted (deactivated) are completely unrelated. has anyone had the similar issue or any ideas how to fix this?

I have attached couple photos. one shows the destroy event configuration, and another one shows database rows, the top ones are deactivated after create event of the bottom row. about 4 to 6 rows are deleted every time.

please let me know if you have some ideas. Thank you in advance

Hi Telerik,

The scheduler take too long time to ready when load with 2000 events in the agenda view.

Is there any way that we can do to improve the performance?

I set grid editable option

editable : { createdAt : 'bottom' }

but

when adding a row with a filter applied, the row to be added does not appear in the last row. (appear randomly)

set filter options

{
  logic: 'or',
  filters: [{field: 'name', operator: 'eq', value: ''}, {field: 'name', operator: 'contains', value: 'Jane'}],
}

how can i do?

Is there a way to setup Kendo UI Scheduler in timeline view to show a time span across midnight?
If startTime and endTime are in the same day all works fine, if I set two different days it show nothing.

I created two dojo examples. They are different only for startDate and endDate

(working, single day) http://dojo.telerik.com/@purchased.software@deltatre.com/Otale/2

(not working, across days) http://dojo.telerik.com/@purchased.software@deltatre.com/OTUmA

Thanks!

Hi, I just discovered your filter component and that's exactly what we need for bridge24.com.

I tried it in that dojo, to find how I can use it with custom data source (users, ...), change the operators, add new types, ... and it works fine.

You can see my tests there

https://dojo.telerik.com/@foxontherock/iYelAJiP/4

There is 1 thing I was unable to do, it's use a previewFormat for values that are array of id, exemple "users" (multi) in my example.

Data values are [1,3], an array of "id". 

Is it possible to use a function in the previewFormat property, to return usernames instead of useridin the expressionPreview property?

Thank you.

Hello ..

I made the kendo Grid widget.

How to adjust the number of lines per page to the current height of the hang and height of the entire grid object?

And how will this change when the height of the grid object changes?

Paweł 

Hi, we updated our kendo version to the latest, and we found something strange.

I know, it's our fault, we shoud not "re-create" a kendo item, but we should check for widgetInstance, or .data("kendoxxx") before creating it.

But, in the previous version, we did not have that bug.

I think that you try to do your best to give us in return the previous instance if it already exists, but in that case, you did something more.

Look at this.

https://dojo.telerik.com/@foxontherock/eCiRiFaZ

If I use setOptions ( in button click), no issue.

If I use kendoListView, to "re-create" it (in fact I don't want it to be re-created, but anyway...) it looks fine, but if you "inspect element", you will see an empty "k-listview-content" generated every time.

We adjust our code to check if the component is already created before creating it.  

But I take time to mention it to you, because in the previous version, it was working without problems, when we tried to re-create a component by mistake.