Hi,
I'm trying to create a cascading drop down list where the child (Order) is still enabled when the parent (Customer) has not been selected, as non selection means All Customers. i.e. the parent is the filter, so when its set to a particular value, the child shows the Orders that belong to that Customer, but when its not selected, the child should show all Orders.
I have tried setting AutoBind to true, but that doesn't seem to help.
Is this possible?
Thanks,
Chris
@(Html.Kendo().DropDownList()
.Name("Order")
.DataTextField("Text")
.DataValueField("Value")
.DataSource(source =>
{
source.Read(read =>
{
read.Action("OrderList", "List")
.Data("filterOrders");
})
.ServerFiltering(true);
})
.OptionLabel("Please Select")
.AutoBind(true)
.CascadeFrom("Customer")
.Enable(true)
Script
function filterOrders() {
return {
customerID: $("#Customer").val()
};
}
I'm trying to create a cascading drop down list where the child (Order) is still enabled when the parent (Customer) has not been selected, as non selection means All Customers. i.e. the parent is the filter, so when its set to a particular value, the child shows the Orders that belong to that Customer, but when its not selected, the child should show all Orders.
I have tried setting AutoBind to true, but that doesn't seem to help.
Is this possible?
Thanks,
Chris
@(Html.Kendo().DropDownList()
.Name("Order")
.DataTextField("Text")
.DataValueField("Value")
.DataSource(source =>
{
source.Read(read =>
{
read.Action("OrderList", "List")
.Data("filterOrders");
})
.ServerFiltering(true);
})
.OptionLabel("Please Select")
.AutoBind(true)
.CascadeFrom("Customer")
.Enable(true)
Script
function filterOrders() {
return {
customerID: $("#Customer").val()
};
}
Hello Felix,
Currently, the API does not expose such functionality, but it is achievable with some custom implementation. However, if you have an idea of a specific functionality that the DropDownList could be improved with, we would suggest logging a feature request in our Feedback Portal. If you decide to log it, please elaborate more on how you envision this functionality to work.The feature requests logged in the portal are reviewed and, based on the interest the community shows in them, they are planned accordingly for implementation in subsequent releases.