Hi Isomorphic,
retesting this issue I wondered why there is a new request when the full dataset is loaded and the filter gets only narrower. See the criteria in the two requests here, where I used the multiple-SelectItem for "Unit" in the modified sample:
to:
The full ResultSet is 17 or 14 records. IMHO it should be possible to do this purely clientside.
This does work if I do e.g. this:
This is also what you describe in the adaptiveFilterFS sample.
Somehow I assumed ResultSet.useClientFiltering would suppress the request in both cases.
I also wonder about the docs:
In the 2nd case, where it works, the criteria is not blank, so I assume the docs are wrong here. If the Unit-equals-array situation from above is expected, it would also be good if there was a description here on when the useClientFiltering actually is expected to work. I think I remember you saying that the framework can't always recognize if criteria will result in a subset of the current data.
Best regards
Blama
retesting this issue I wondered why there is a new request when the full dataset is loaded and the filter gets only narrower. See the criteria in the two requests here, where I used the multiple-SelectItem for "Unit" in the modified sample:
Code:
data:{
operator:"and",
criteria:[
{
fieldName:"units",
operator:"equals",
value:[
"Pad",
"Ream",
"Tin"
]
}
]
},
Code:
data:{
operator:"and",
criteria:[
{
fieldName:"units",
operator:"equals",
value:[
"Pad",
"Ream"
]
}
]
},
This does work if I do e.g. this:
- Enter "Addi" in the filterRow for name, press Enter
- Request with 44 rows returned
- Change to "Adding", press Enter
- No request, but 6 rows displayed
This is also what you describe in the adaptiveFilterFS sample.
Somehow I assumed ResultSet.useClientFiltering would suppress the request in both cases.
I also wonder about the docs:
Whether to filter data locally when all DataSource records have been loaded (that is, criteria is blank and cache is complete).
Best regards
Blama
Comment