We have a project with Telerik MVC Extensions which we're migrating it to Kendo UI. There's only one significant issue when using ForeignKey columns in Grids.
I believe that this is caused by the EditorTemplate file GridForeignKey.ascx. When it's using a Telerik DropdownList it does not work 100% properly in Kendo Grids, when I set it to Kendo, it does not work 100% properly on old Telerik grids.
How can I set to Kendo use a different one for its foreign key? We have added Kendo EditorTemplate to EditorTemplates\Kendo folder.
Thanks,
Ezequiel
I believe that this is caused by the EditorTemplate file GridForeignKey.ascx. When it's using a Telerik DropdownList it does not work 100% properly in Kendo Grids, when I set it to Kendo, it does not work 100% properly on old Telerik grids.
How can I set to Kendo use a different one for its foreign key? We have added Kendo EditorTemplate to EditorTemplates\Kendo folder.
Thanks,
Ezequiel
2 Answers, 1 is accepted
0
Accepted
Hi,
Basically the Telerik Extensions for MVC Grid can work with KendoUI editor templates if all scripts are correctly included in the page - please check this screencast. Alternatively you can prefix the KendoUI ForeignKeyColumn editor template file name and then specify the new name in all KendoUI Grids:
Also as Telerik Extensions for ASP.NET MVC has reached its official End of Life (EOL), with no additional fixes or enhancements expected in the future, I would strongly suggest to migrate all widgets to Telerik UI for ASP.NET MVC as we no longer provide support for the Telerik Extensions.
Regards,
Vladimir Iliev
Telerik
Basically the Telerik Extensions for MVC Grid can work with KendoUI editor templates if all scripts are correctly included in the page - please check this screencast. Alternatively you can prefix the KendoUI ForeignKeyColumn editor template file name and then specify the new name in all KendoUI Grids:
columns.ForeignKey(p => p.EmployeeID, (System.Collections.IEnumerable)ViewData["employees"], "EmployeeID", "Name") .EditorTemplateName("KendoGridForeignKey");Also as Telerik Extensions for ASP.NET MVC has reached its official End of Life (EOL), with no additional fixes or enhancements expected in the future, I would strongly suggest to migrate all widgets to Telerik UI for ASP.NET MVC as we no longer provide support for the Telerik Extensions.
Regards,
Vladimir Iliev
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Ezequiel
Top achievements
Rank 2
Rank 2
answered on 25 Apr 2014, 02:47 PM
Thanks. We're migrating some parts as we also have new stuff, we'll have a lot of work as it was about 3 years of dev in Telerik MVC with about 7 developers, so we have a lot of MVC extensions widgets. I believe it will be work for at least the end of the year.