Last Updated: 21 Jun 2022 10:42 by ADMIN
Created on: 29 Nov 2012 11:36
Category: Data Source
Type: Feature Request
Support composite keys in the DataSource ID property
At the moment, the DataSource only uses one field for its ID property (if you enter several, then only one is used, apparently).  This doesn't reflect reality, in that in many cases (where one record is a child of another), the key field for a database table is a composite (from 2 or more fields).  
The existing situation causes problems in inline editing of the KendoUI grid, because default values need to be set for foreign key fields, but if these are set to a valid value, then spurious calls to the Inline_Create method occur because the DataSource treats the record as a new record when it is not.
In any case, allowing multiple fields would simply reflect reality.
Angel Petrov
Posted on: 21 Jun 2022 10:42


There are corner cases when it comes to a composite keys. That said satisfying all conditions may be difficult. When having a particular problem I would recommend opening a formal support ticket and posting the problematic code there so it can be revised and further assistance on the specific matter can provided.

Angel Petrov
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Posted on: 14 Jun 2022 15:49

This really needs to be looked at.  We implemented a method to pass two values back to the controller when editing but when you cancel edit, the grid puts the wrong record back.


Posted on: 14 Jan 2022 09:41

Hello Scott,

Thank you for the feedback.

I have raised this matter to the Dev team and they are working on it. I will follow up once I have more information.

Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Posted on: 08 Jan 2022 04:09

Surprised and very disappointed that multi-column primary keys are not supported. This severely limits the usefulness of the DataSource, and since the DataSource is at the heart of--well, just about EVERYTHING in KendoUI--we will probably start looking at other UI frameworks when our license comes up for renewal.

Posted on: 02 Jul 2020 09:46

Hello Kevin,

This feature is currently not planned for a release. However, once it gets placed in the RoadMap it will receive a status Planned and later on Completed when it is live.

Addityioanlly, you can click on the Follow button to receive automatic updates about status changes.

Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.
Posted on: 25 Jun 2020 19:00
How can I track the release of this feature request? 
Asiri Dissa
Posted on: 03 Jun 2020 02:35
Still not in place?
This is a valuable addition to the framework. Hope you are working on this.
Posted on: 24 Dec 2019 12:53

Hi Alexander,

Thank you for bringing this feature request back to our attention. I can definitely see the value in it so I uplifted its priority and it will be reviewed by the Product Management for future planning and implementation.

    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.
    Posted on: 18 Dec 2019 02:26

    I use Kendo with a SQL data warehouse with a normalised star schema design in order to achieve scalable performance and parallel operation. This uses large sets of fields as a primary key so the suggested workaround of creating a psuedo key by concatenating just wouldn't be feasible.

    The only workaround for this design is to include a separate ID field for use only with Kendo. This destroys performance and has forced us to avoid using Kendo for CRUD operations whenever possible.

    I think it's about time composite keys were supported so this can be a true option for use with enterprise grade applications.

    Posted on: 02 Apr 2019 14:12
    I am surprised that a professional and enterprise-strength toolset like this product still does not support composite keys after all these years. Let's make it happen! :)
    Posted on: 19 Feb 2018 17:22
    I worked around this with a pseudo key as suggested in this post. https://www.telerik.com/forums/composite-datakey-in-kendo-ui-mvc#JlhcEtSyAEqMWaW6TjnDKQ
    Posted on: 23 Aug 2014 19:45
    I have used the following workaround to solve this. 
    Usually I have to use buddy or ViewModel classes in the grid, rather than the raw entity framework (or other) classes from the database itself, because the raw classes usually have circular object graphs (because they have parent child relationship fields). 
    In the code to create buddy/viewmodel classes from the raw classes, I populate an extra field that I've added to the buddy classes, IDForKendoTemplate, and I give this a unique value (i.e. 1, 2, 3, sequentially) for each object that is converted.  I can then use that field as the ID for kendoUI grids, and to identify parent grids uniquely in templates.
    Posted on: 15 May 2013 21:53
    I ran into this too.  A UI framework shouldn't really force us to have our data stored in a certain way to be effective.