2 dropdownboxs, filtering second off the the value in first

Question

Hello,
This seem logically simple to me, I had 1 dropdownbox that filters the results of the other dropdownbox
Was using the model filter but was unable to get it working with how I have my dropdownboxs setup, then I tried using a formatter but again wasn't able to get it working.
I created a separate version of my dropdownboxs using binditems and was able to kind of filter the second box, instead of how I have them done below but had issues with the keys being saved to the model.
Anyone have any idea currently how to get it work with how I have it setup?
        var oDropdownBox1 = new sap.ui.commons.DropdownBox({
            selectedKey: "{division}",
            items: {
                path: "/divisions",
                template: new sap.ui.core.ListItem({
                    text: "{divisiondesc}",
                    key: "{division}"
        var oDropdownBox2 = new sap.ui.commons.DropdownBox({
            selectedKey: "{bus_unit}",
            items: {
                path: "/bunits",
                template: new sap.ui.core.ListItem({
                    text: "{busunitdesc}",
                    key: "{busunit}"
        oTable.addColumn(new sap.ui.table.Column({
            label: new sap.ui.commons.Label({
                text: "Divs",
                required: true
            template: oDropdownBox1,
            width: "150px",
            hAlign: "Center"
        oTable.addColumn(new sap.ui.table.Column({
            label: new sap.ui.commons.Label({
                text: "Bus"
            template: oDropdownBox2,
            width: "150px",
            hAlign: "Center"
oTable.bindRows("/entries");
The table is bound to the entries node, and in the entries node is division and bus_unit for the actual value displayed in the table and saved for the entry.
Then the list items of the 2 columns are bound to their correct nodes, i.e. "/division" and "/bunits". To filter the listitems of bunits I use"division" . Both "divisions" and "bunits" have division on them, so it should quite simple to filter the second box :/.
This is quite simple logically but can't seem to get it to act how I want!
Any help would be appreciated. Thanks!

Answer 1

To be honest, I would have expected it to work in the following way:
            var oTable = new sap.ui.table.Table()
                .addColumn(new sap.ui.table.Column({
                    label: new sap.ui.commons.Label({
                        text: "Division"
                    template: new sap.ui.commons.DropdownBox({
                        selectedKey: "{tablemodel>division}",
                        items: {
                            path: "metadatamodel>/divisions",
                            template: new sap.ui.core.ListItem({
                                text: "{metadatamodel>divisiondesc}",
                                key: "{metadatamodel>division}"
                .addColumn(new sap.ui.table.Column({
                    label: new sap.ui.commons.Label({
                        text: "Business Unit"
                    template: new sap.ui.commons.DropdownBox({
                        selectedKey: "{tablemodel>bus_unit}",
                        items: {
                            path: "metadatamodel>/bunits",
                            template: new sap.ui.core.ListItem({
                                text: "{metadatamodel>busunitdesc}",
                                key: "{metadatamodel>busunit}"
                            filters: [new sap.ui.model.Filter("division", sap.ui.model.FilterOperator.EQ, "{tablemodel>division}")]
                .bindRows("tablemodel>/");
(See also the full example on JSBin)
As you can see, I have two models, one for the table data ("tablemodel"), and one specifically for the dropdown items ("metadatamodel")
In the second dropdown, you see I have set a filter on field 'division' which is being filtered on the current 'tablemodel>division' value, but for some reason I couldn't get it to filter properly... it appears as if the value binding in the filter is not "ready" and thus filters on a non-existing value.
If you replace the filter value "{tablemodel>division}" with "div1" for example, then the filter obviously works, but then it's not dynamic anymore... So yeah, I am now curious to see it working too
BTW, if it were outside a table then it wouldn't be a problem; the problem is definitely with the dynamic filter binding with dynamic table data