I am following the sample instructions from the link: https://www.telerik.com/kendo-angular-ui/components/grid/data-operations/data-binding/automatic-operations/#toc-custom-directives

In the ProductsBindingDirective, the rebind method calls the service passing the state of the grid.

In the ProductsService which extends NorthwindService (extending BehaviorSubject), the fetch method sends a request to the Base_URL with the grid state info passed as query string parameters, e.g. https://odatasampleservices.azurewebsites.net/V4/Northwind/Northwind.svc/Products?$orderby=UnitPrice&$count=true&$skip=0

Question: Does the Northwind.svc execute a SQL query for every fetch method request, and rebuild a new result set based on the query string parameters? Or does it execute the SQL query once, and applies the query string parameters criteria (skip, orderby, pagesize, etc)  on the same result set initially retrieved?

In my case, I have a query returning tens of thousands of records, so I want to confirm which component is processing the grid state information. Should the ProductsService (being a BehaviorSubject) keep the initial big result set as its own property and apply the grid state criteria, or does it just pass the grid state to the server and expect to receive the correct data?

Thanks!

The Angular MultiSelect dropdown control normally opens the dropdown popup when you click inside the search text box. But its not happening in one particular scenario in which you click right next to the last selected value (still inside the search text box). 

So if you have selected some values already and you want to open up the popup again to select more then you have to click approximately a couple of centimeters away from the last selected value in the text box. I can see this happening in the simple demo available in the documentation as well.

Has anybody else observed the same?

Hi,

Assume I have a datasource with ID and Name fields. I display the Name but the main field is ID. I manage to show the right Name and get the ID with a combobox in Edit and Add mode. But how can I fix the filter for Name?

TL;DR: Any plans for virtualisation support on Treeview?

I've attached an example project.

The data is a set of companies. Each company has 5 offices. Each office has a collection of Drivers and a collection of Vehicles. There are 1000 Drivers and 1000 Vehicles in each.

1: Run the app
2: Expand a company
3: Expand an office
4: Expand one of the child nodes (Drivers or Vehicles)

On my computer, this takes about 7 seconds to open. I think it is a combination of adding so many DOM elements and also using an ng-template inside the tree.

This might improve in Angular6, but it seems that creating all of those DOM elements is a waste of resources anyway. Do you have any plans for supporting virtualisation in your Treeview component?

I'm getting this error:

ERROR in node_modules/@progress/kendo-angular-buttons/dist/es/navigation/navigation-config.d.ts(1,10): error TS2305: Module '".../node_modules/@angular/core/core"' has no exported member 'OpaqueToken'.

Using @angular/core version 5.2.9

I've been trying at this for a couple days and noticing the same thing, ie. that I can get a combobox to read back selected values and record them successfully to a grid, I can get a combobox on its own to take and save the new custom values to my back-end through REST, but I can't combine the two.

As far as the API's are concerned this combination works for in-grid selection:

          <kendo-combobox [formControl]="dimensionTypeGridFormGroup.get('dimensionTypeId')"
                          [data]="dimensiontypes"
                          [textField]="'name'"
                          [valueField]="'id'"
                          [valuePrimitive]="true">
          </kendo-combobox>

This for creating new content:

<kendo-combobox [allowCustom]="true"
                [data]="combolists"
                [textField]="'name'"
                [valueField]="'id'"
                [valueNormalizer]="valueNormalizer"
                [(ngModel)]="clbuilder">
</kendo-combobox>

It seems like the moment I add [allowCustom] to a combobox in a grid cell it causes two things to happen:

1) the grid cell will be blank on save

2) only the default value is saved in the grid formgroup for that cell.

In a lot of cases I could indeed save my new record to my back end but the grid would stop working. In some of my trial and error I noticed that confusion was occurring (in the combobox API references) between the form control data and the combobox data (such as 'id' in the formGroup vs. in the export interface array). 

Is there a right way to do this through the combobox API components and, if not, is there a way that I could push the values I need back to the grid from somewhere else like a valueChange or valueNormalizer method? I remember there being an edit.service push back to grid in the in-cell grid editing example but I'm not sure how to hit that from within a component yet.

Take a look at this Plunker:

https://plnkr.co/edit/SyfbOR4dlMqbB3FJwGzR?p=preview

What I'm trying to achieve is specifying a set of grid-columns using Angular ngFor and ngSwitch directives. Using ngFor renders fine, but once I try to introduce ngSwitch, it renders as if there were not grid-column components.

It should be possible but I'm wondering if I'm missing something?

Thanks.

I've been reading through the tutorial on creating a Master-Detail grid for Angular 4/5 and so far have been able to construct a working mock-up in VS Code without any significant roadblocks.

My current question: is it possible to retrofit the Master-Detail grid for API data received by JSON? If so what approach would you recommend - building the GridDataResult data input array within the component hosting the grid (such as is done with the programming in the grid edit examples) or is there a kendo-data-query module similar to toODataString that I can use to similar ends in northwind.services.ts under fetch and in the queries?

Eventually I'd like to incorporate full CRUD capabilities with most layers and for that reason I'm hoping to keep the read operation in the same API format as the edit, update, and delete.