Strange problems when "minimumSearchLength" is set

[pavo123]

Hi Isomorphic,

modifing this sample with this code

isc.DynamicForm.create({
    ID:"testForm",
    width: 500,
    fields : [
    {
        name: "filteredCombo", title: "Select Item", editorType: "ComboBoxItem",
        minimumSearchLength: 3,
        addUnknownValues:false,
        optionDataSource: "supplyItem", 
        displayField:"itemName", valueField:"SKU",
        filterFields:["SKU", "itemName"],
        pickListPlacement: "fillScreen",
        pickListWidth:300,
        pickListFields:[
            {name:"SKU"},
            {name:"itemName"}
        ]
    }
    ]
});

I noticed strange behavior:

• After clicking on CBI all records are fetched although minimumSearchLength is 3
• After 1st step, if I type >=3 letters, message "Enter a longer search string to search" is still there (no fetch at all).

Best regards
Pavo

[Isomorphic]

We've made some changes to resolve this issue. Please try the next nightly build dated Dec 21 or above (12.0 and 12.1 branches)

Regards
Isomorphic Software

[Blama]

Hi Isomorphic,

it's way better using v12.0p_2019-12-21, thank you.

There is a minor issue and a very strange observation left. minimumSearchLength: 0 (which does not make sense, then one can leave it at null) results in too many fetches in many situations. Perhaps you could warn here.

In the same setting there is a strange situation where a fetch "waits" and is only executed when I click "Clear" in the RPC request tab of the Developer Console. This does not make any sense to me at all.

Please see this video to see both effects.

• Minor: 2 fetches for null and ""
• Strange: Click on Sample's "Cancel", waiting a long time on Developer Console "Clear" until the click here and then the new fetch directly after the click (watch the clock in the video and timestamps in the Developer Console)

isc.DynamicForm.create({
    ID:"testForm",
    width: 500,
    fields : [
    {
        name: "filteredCombo", title: "Select Item", editorType: "ComboBoxItem",
        minimumSearchLength: 0,
        addUnknownValues:false,
        optionDataSource: "supplyItem", 
        displayField:"itemName", valueField:"SKU",
        filterFields:["SKU", "itemName"],
        pickListPlacement: "fillScreen",
        pickListWidth:300,
        pickListFields:[
            {name:"SKU"},
            {name:"itemName"}
        ]
    }
    ]
});

Best regards
Blama

[Isomorphic]

Thanks for the notification. We'll take a look at these issues and get back to you

[Isomorphic]

We've made some changes to address this odd behavior with minimumSearchLength set to zero

Please try the next nightly build (Dec 31 or above)
Regards
Isomorphic Software

[Blama]

Hi Isomorphic,

this is fixed for me using v12.0p_2020-01-04, thank you.
Out of interest, because I have not noticed this behavior anytime before: Can you explain in simple words what the reason for this delayed Clear-Button related fetch was?

Best regards
Blama

[Isomorphic]

The basic overview is that there was a fetch inappropriately being queued up to be performed on blur, and by hitting the clear button in the dev console you were taking focus from the item and allowing that fetch to get kicked off