Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    [bug] DataBound SelectItem with defaultValue doesn't display the value

    SmartClient Version: v10.1p_2016-03-29/Enterprise Development Only (built 2016-03-29)
    and
    SmartClient Version: SNAPSHOT_v11.0d_2016-03-27/EVAL Development Only (expires 2016.05.26_09.22.33) Licensed to: Isomorphic Software (#ISC_EVAL_NIGHTLY)

    Chrome on OSX

    Please modify the #formDependentSelectsDatabound sample like this:

    Code:
    isc.DynamicForm.create({
        top: 25,
        width: 500,
        numCols: 4,
        autoDraw: true,
        fields: [
            {
                name: "itemName1", title: "Item",
                optionDataSource: "supplyItem", displayField: "itemName", valueField: "itemID",
                defaultValue: 1,
                editorType: "SelectItem",
                visible: true,
                required: true
            },
            {
                name: "itemName2", title: "Item",
                optionDataSource: "supplyItem", displayField: "itemName", valueField: "itemID",
                defaultValue: 2,
                editorType: "SelectItem",
                visible: true,
                required: true
            }
        ]
    });
    Basically there are two selectItems dataBound to the same dataSource. That seems to be the key to reproduce the problem.

    You'll see that the first SelectItem remains not editable and displays the 'Loading' message.

    #2
    We're reproducing this issue and are working on it.
    In the meantime a quick workaround is to set the cachePickListResults property to false on these SelectItems

    We'll follow up when we have a proper fix in place

    Regards
    Isomorphic Software

    Comment


      #3
      Thanks (and the workaround is working perfectly).

      Comment


        #4
        SmartClient Version: v11.0p_2016-05-19/EVAL Development Only (expires 2016.07.18_04.37.00) Licensed to: Isomorphic Software (#ISC_EVAL_NIGHTLY)

        Hello, it seems that this is now fixed, isn't it?

        Comment

        Working...
        X