Hi Yuki,

Thank you for above example. After working on it I found there was a set up issue. As a side note after reading the documentation I can see on demand feature does not support paging which is a very important feature when you need to show for example page 4. I found a work around to this, loading desired value at the first position. However it would have been a good extension for this feature since it is remote. I think this ticket can be closed. Thanks for your help. 

Hello cristian,

After reviewing Development ID of 251110, this is the default behavior of igCombo. When the user closes the drop down clearfiltering is called in order all the items to be previewed next time when he opens the drop down.

If the user does not want to make requests to ComboData, he can set the filteringType to ‘none’. If the user wants filtering, but does not want clear filtering to be called after closing drop down, he can cancel the event filtering if it is called from dropDownClosing:

$(function () {
        var clearFilterCalledFromClosingDD = false;
        $("#type_combo").igCombo({
            …
            filteringType: 'remote',
     …
            dropDownClosing: function (evt, ui) {
                clearFilterCalledFromClosingDD = true;
            },
            filtering: function (evt, ui) {
                if (clearFilterCalledFromClosingDD) {
                    clearFilterCalledFromClosingDD = false;
                    return false;
                }
            }
        });
})

If you have any question with this, please let me know.

Thank you Yuki, You can close this ticket. I will keep on eye it. I found a work around, but its just a work around

Hi Yuki,

I am following up on this, do you have any inputs? I stop my tests with IgCombo as a IgGrid column since most of the futures does not work out of the box. So I carry on with IgCombo and I found a really weird behaviour. Not sure why IgCombo is calling twice the datasource url when I apply a filter:

$("#type_combo").igCombo({
    autoComplete: true,
    autoSuggestion: true,
    filteringType: 'remote',
    loadOnDemandSettings: {
        enabled: true,
        pageSize: 20
    },
    responseDataKey: "data",
    responseTotalRecCountKey: "recordCountKey",
    dataSource: location.protocol + "//" + location.host + '/Controller/Get?Id=' + model.id,
    dataSourceType: 'json',
    textKey: "creditor_code",
    valueKey: "creditor_id",
    filterExprUrlKey : "filter",
    headerTemplate: '<div class="boxed">List</div>',
    footerTemplate: '<div class="boxed">Count: {0} of {3}</div>',
    nullText: 'No Result',
    dropDownOrientation: "bottom",
    itemsRendered: function (evt, ui) { return itemsRenderedCombo(evt, ui); }
});

function itemsRenderedCombo(evt, ui) {
    $("#type_combo").igCombo("value", journalModel.id);
}

I debug this funky behaviour and I found that trying to set up the value at itemsRenderedCombo. $("#type_combo").igCombo("value", model.id); makes the IgCombo to call again the DataSourceUrl, but the second time with an empty value as a filter. I ended up returning (second call when filter is empty) the first page for On demand feature instead. So is there any way to set up IgCombo value at itemsRenderedCombo so I can show the id? if I comment out Bold line of code. Then filter works, but if I save the result as it is. id will be null instead of keeping the id which was set up before doing the filter search. Is there any way to bypass the second call? or is there another way to set up igCombo value so I can keep a consistency on id/combo value?

type a filter 

Hello cristian,

Would you provide me with the configuration of igCombo, and I will check the behavior based on your option setting.

Thank you in advance.