Until 1Q2016 comes out, I'll have to manage the cascading
myself. Unfortunately, this isn't a super straight-forward problem I'm working
on. I've updated the jsFiddle and hope you can take a look and point me in the
right direction on a couple of fronts. I've updated the local dataSource for
the dropdowns to be a dictionary (table: columns) of dictionaries (column:
column details). I’ve created a local dataSource for the initial grid data
(eventually grid data will all be remote).
When I click "Edit", all fields should be editable, but if the user changes the table selection, the column, comparison, & value should be disabled. They should be enabled when a table is selected. Same with “Add New Record” – when a new record is added, only Table should be editable and perhaps Logic field if it not the first row (see bullet below for Logic).
The Value column - based on the column selection, the value column should initialize the widget appropriate for the data type. I have the data type as a column in the dataItem. What is the best way (and where) to initialize that <input> as the proper widget?
Right now, "Add New Record" isn't doing anything. What am I missing?
For the first row only, the Logic field should be non-editable and blank (or even better, static text of "WHERE")
Note, I think this sort of example would be really great
to show in the list of grid demos you have on the site - a complex inline
editing where the fields are cascading, the values may be different widget