Colum.Member is always "undefined" in Ajax Read Method (2013 Q2)

3 posts, 1 answers
  1. BigzampanoXXl
    BigzampanoXXl avatar
    68 posts
    Member since:
    Jan 2007

    Posted 17 Jul 2013 Link to this post


    it seems a new has been introduced with the 2013 Q2 release. With Release 2013 Q1 SP it worked fine.

    I have a ajax grid and have the "Member" property set on the columns, so I will know which column was clicked for sorting when reaching the ajax read method on the controller.
    Here is a snippet of the razor view where I have set the "Member" property on the columns:
    columns.Bound(c => c.ItemAttributes)
                           .ClientTemplate("#=gridClientTemplate(Unread, 'begin')#" + template + "#=gridClientTemplate(Unread, 'end')#")
                           .Column.Member = Model.FolderColumns[id].ColumnUniqueName;
    When I click on a the header of the column the Ajax Read Method is called. Now the problem is, that I always get "undefined" instead of the clicked Column-Name in the request.Sort[INDEX].Member property. Please take a look at the attached screenshot.

    This is a very serious bug in the 2013 Q2 release, cause I can't do the column sorting anymore. Please try to fix that bug as soon as possible in one of the next Internal Builds.
    If you need any more infos, just tell me. Thanks.
  2. Answer
    Nikolay Rusev
    Nikolay Rusev avatar
    2289 posts

    Posted 18 Jul 2013 Link to this post

    Hello Dietmar,

    Unfortunately this is an omission on our side. I believe we've managed to address the issue. It was related to how complex field names are resolved for sort/filter/group descriptors.

    The fix will be available in next internal build.

    Nikolay Rusev
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
  3. BigzampanoXXl
    BigzampanoXXl avatar
    68 posts
    Member since:
    Jan 2007

    Posted 24 Jul 2013 Link to this post

    Thank you very much. I just read the Revision Log of Internal Build 722 and indeed it seems to be fixed.

Back to Top