Ext version tested: Browser versions tested against: DOCTYPE tested against: Description:

  • We have a set of comboboxes where we want to bind both the store and the value. In most cases, this works fine, but in one particular case the combo is sensitive to the order of the keys in the bind:{} config. If you place the value above the store in the bind config for comboboxes where the valueField and the displayField are the same, you will get an exception when attempting to set the value via the view model.

    (There might be other configurations that have this same issue - the displayField != valueField case happened to be the differentiator that we came across. It took a long time to sort that out!!)


    This was especially confusing as the order of keys in javascript objects aren't guaranteed, so it seems like this could cause numerous issues if there is order sensitivity in the bind:{} config.




Steps to reproduce the problem: The result that was expected:

  • All three combos are filled in with value set


The result that occurs instead:

  • Last combo fails setValue, throws error