12.1p ListGrid ListGridField displayed default operator not used

[Blama]

Hi Isomorphic,

please see this modified sample (v12.1p_2023-01-05).
As you can see here after filtering, the GUI looks like it would filter using startsWith, but in reality it uses contains. The request also does not use advancedCriteria, but

data:{
        countryName:"d"
    },

Either adding filterOperator to the ListGridField or setting alwaysShowOperatorIcon: true on the ListGrid fixes the issue, the request is then:

data:{
        operator:"and",
        criteria:[
            {
                fieldName:"countryName",
                operator:"startsWith",
                value:"d"
            }
        ]
    },

Best regards
Blama


countryDS:

isc.DataSource.create({
    ID: "countryDS",
    fields:[
        {name:"countryCode", title:"Code"},
        {name:"countryName", title:"Country", validOperators:["startsWith", "iStartsWith", "endsWith", "iEndsWith", "iregexp", "regexp"]},
        {name:"capital", title:"Capital"}
    ],
    clientOnly: true,
    testData: countryData
})

databound.js (broken like this with filterOperator commented out):

isc.ListGrid.create({
    ID: "countryList",
    width: 500,
    height: 224,
    alternateRecordStyles: true,
    showAllRecords: true,
    dataSource: countryDS,
    autoFetchData: true,
    showFilterEditor: true,
    fields: [
        { name: "countryCode" },
        { name: "countryName"}, //, filterOperator: "startsWith" },
        { name: "capital" }
    ],
    dataProperties: { useClientFiltering: false }
})

[Isomorphic]

Thanks for the report - we've fixed this and it should hit today's builds, dated January 7.

Note that your grid will no longer issue simple-criteria in this case - your validOperators list does not include the default op based on field-type and textMatchStyle of the grid ("iContains"), so you're effectively providing "startsWith", the first entry in the array, as the default, but that op isn't compatible with the grid's textMatchStyle.

[Blama]

Hi Isomorphic,

I don't think the fix fixed the issue - actually it seems that now validOperators is broken. All the default operators are available.
This is what the sample looks like for me using v12.1p_2023-01-08:


Best regards
Blama

[Isomorphic]

We're seeing it work as expected with your code at the link you provided above - did you perhaps forget to change the DS or click Try It on that tab?

[Blama]

Hi Isomorphic,

I still see the erroneous behavior in v12.1p_2023-01-08 and v13.0p_2023-01-08 in FF108 and Edge108.
Did you try in the online showcase as well?

SNAPSHOT_v13.1d_2023-01-09 is working as expected, though.

Best regards
Blama

[Isomorphic]

Yes, we see it working at both online links - you do need to click "Try It" when you change the DS tab, and then again when you change the code tab.

[Blama]

Hi Isomorphic,

sorry, my bad. I did not realize that you had to do this twice.
If I do this it's working as expected in all three versions. Thank you.

Best regards
Blama

[Isomorphic]

Yes, the Try It button only applies changes to the current tab.

We'll answer the questions in your other thread about validOperators shortly today.