Last Updated: 26 Feb 2019 06:37 by ADMIN
Created on: 23 Feb 2019 03:37
Category: UI for ASP.NET MVC
Type: Feature Request
How do I populate a grid control in a splitter window with data resulting from selecting a link in another splitter window containing a tree control?

This request feature is tied to ticket #1388825. Refer to that ticket for the illustration of the problem I am referring to. 

Given two splitter windows, all I require is to populate one splitter window with some data related to the other splitter window.

In my case, one Telerik splitter window has a simple 3-level Telerik tree control. When the 3rd level is clicked on, I want the other Telerik splitter window containing a Telerik grid to display details of what was clicked on. This requires an AJAX call to avoid having to reload the tree control.

However, while working with Support, there seems to be a very high degree of rocket science and uncertainty involved with implementing this scenario. 

I would have thought with great certainty that the functionality I need would be clearly documented somewhere in the Telerik doc database. I am still amazed that I might the first person who has this problem.

So, this feature request is to essentially provide very clear and competent documentation on the design pattern one needs to implement AJAX calls which pass data between two Telerik controls. At the very least, it would document the design pattern for the scenario I described above.

Maybe this cannot be done in the 21st Century yet. I don't know what is involved. I'm just a backend developer who purchased a Telerik license so I would not have to spend the rest of my life trying to learn Javascript.


Thank you,



1 comment
Marin Bratanov
Posted on: 26 Feb 2019 06:37
Hi Jay,

Let's keep this in your ticket or forum thread on this where samples are already available.

There isn't a specific design pattern for this, you need to review the widget's functionality and API and use them together to create the desired application logic. This is the general approach to building applications from separate widgets. The possible integration scenarios are endless and it is not possible to have a ready example for each and every one of them, which is why we first focus on providing comprehensive API reference that shows the developer what methods and properties they can use, so they can combine them into a complete app.

In this case, this involves the following:

  1. binding the treeview to a remote data source so you can easily provide metadata to its nodes
  2. using the select event of the tree to get that metadata
  3. use the other widget's API along with that data, for example:

Unfortunately, for the time being, JavaScript is necessary for front-end development. Maybe Blazor will change that in the future and we're monitoring that, but not yet.

Marin Bratanov
Progress Telerik
Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.