Enable cascading comboboxes when editing existing record

6 posts, 0 answers
  1. Shawn
    Shawn avatar
    49 posts
    Member since:
    Jul 2011

    Posted 18 Sep 2012 Link to this post

    I have a grid that is configured for Ajax editing, and records are edited/added by means of a popup that displays a custom template that contains a number of cascading comboboxes.  It works beautifully for adding a new record.
    However, when editing an existing record, all comboboxes have the right value from the bound record being edited, but they are all disabled (except the first one, of course).  So if a user wants to change the value in the last combobox, they must first go through the processes of selecting a different value in each of the other comoboxes, starting at the root one. This is of course cumbersome.  How can I make it that when editing an existing record, all comboboxes are enabled so that the user can go straight to the last one in order to change its value.
    Here's how my comboboxes are defined (this is one of 9 cascading combos):
    @(Html.Kendo().ComboBoxFor(m => m.Tier2)
            .Placeholder("--Select a Tier 2--")
            .DataSource(ds => {
                ds.Read(rd => {
                    rd.Action("GetTier2", "Budget").Data("dataForTier2");
                })
                .ServerFiltering(true);
            })
            .DataTextField("TierName")
            .DataValueField("TierCode")
            .Enable(true)
            .AutoBind(false)
            .CascadeFrom("Tier1")
      )


    Thanks for a great product.
  2. BobDev
    BobDev avatar
    5 posts
    Member since:
    Jun 2009

    Posted 25 Oct 2012 Link to this post

    I agree. This same situation would occur if the parent combobox is pre-populated for a new record. I cannot get the child combobox out of disabled mode unless I manually change the parent value.
  3. UI for ASP.NET MVC is VS 2017 Ready
  4. Brian LeBaron
    Brian LeBaron avatar
    2 posts
    Member since:
    May 2010

    Posted 28 Nov 2012 Link to this post

    Any luck with this? I'm running in to the same exact problem. Seems like a common thing to do...
  5. Shawn
    Shawn avatar
    49 posts
    Member since:
    Jul 2011

    Posted 28 Nov 2012 Link to this post

    This was resolved for me in the 2012 Q3 release.
  6. John
    John avatar
    9 posts
    Member since:
    Nov 2010

    Posted 11 Dec 2012 Link to this post

    We are  using  Q2 release of Kendo

    What needs to be done to use this particular Q3 fix Combobox behaviour in our project

    Is it enough to refer latest  kendo.combobox.min.js file?

    Thanks
    Jaffar

    Please copy me when you reply to this post sharfuj@chesterton.com
  7. Sebastian
    Admin
    Sebastian avatar
    9934 posts

    Posted 12 Dec 2012 Link to this post

    Hello Chris,

    Yes, it should be sufficient to reference the latest combobox scripts in case the recent update addresses the issue discussed in this thread.

    Kind regards,
    Sebastian
    the Telerik team
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
Back to Top
UI for ASP.NET MVC is VS 2017 Ready