DynamicForm: a FormItem 'inherits' PickList from another ComboBoxItem

[claudiobosticco]

SmartClient Version: v11.0p_2016-05-06/EVAL Development Only (expires 2016.07.05_07.36.49) Licensed to: Isomorphic Software (#ISC_EVAL_NIGHTLY)
SmartClient Version: SNAPSHOT_v11.1d_2016-05-11/AllModules Development Only (built 2016-05-11)

Chrome on OSX

Hello, please modify the #formDependentSelectsFS sample like this:

isc.DynamicForm.create({
    width: 500,
    fields : [
       {
        name: "itemName", title: "Item Name", editorType: "ComboBoxItem", pickListWidth: 250,
        editorProperties: {optionDataSource: "supplyItem", valueField: "itemID", displayField: "itemName"} 
       },
       {name: "anotherField", type: "integer"}
    ]
});

You'll see that the 'anotherField' item becomes a selectItem with the same pickList as 'itemName'.

[Isomorphic]

Thanks for the notification. This appears to be a problem with the sample / feature explorer harness only. We'll get it fixed, but it shouldn't effect any applications, etc.
If you are seeing anything similar in a real app, please let us know.

Regards
Isomorphic Software

[claudiobosticco]

Actually I put together the test case after seeing the problem in a real application. It was a DynamicForm without a dataSource, with a ComboBoxItem (with optionDataSource) and other 3 FormItems of various type, and each of them showed the same pickList, even a selectItem with a valueMap.
Something like this:

isc.DynamicForm.create({
    width: 500,
    fields : [
       {
        name: "itemName", title: "Item Name", editorType: "ComboBoxItem", pickListWidth: 250,
        editorProperties: {optionDataSource: "supplyItem", valueField: "itemID", displayField: "itemName"} 
       },
       {name: "item1", type: "integer"},
       {name: "item2", type: "select", valueMap:{foo:3, bar:5}},
       {name: "item3", type:"text" }
    ]
});

Actually I've just tried with build
SmartClient Version: v11.0p_2016-05-12/EVAL Development Only (expires 2016.07.11_07.39.10) Licensed to: Isomorphic Software (#ISC_EVAL_NIGHTLY)
and it seems fixed.

[Isomorphic]

Interesting.
We definitely did have a problem with the Feature Explorer which could produce an effect similar to what you were describing, but wouldn't have caused any problems elsewhere, so this must have been an unrelated problem.

Anyway - glad to hear it's fixed with the latest build.

Regards
Isomorphic Software