using v12.1p_2022-10-18 and the testcase from #13 the exception is gone and there is no fetch for the 2nd button, like you say.
This already helps and together with your explanation from #14 I'm pretty sure that also my ResultSet-warning, that I could never explain, but that also did not cause problems, will be gone.
There is another issue, though: I believe the criteria is applied twice. See this request for a click on the 1st button.
Best regards
Blama
Code:
{ dataSource:"worldDS", operationType:"fetch", componentId:"filterGrid", data:{ operator:"and", criteria:[ { fieldName:"continent", operator:"inSet", value:[ "Africa", "Asia", "Australia/Oceania", "Europe", "North America", "South America" ] }[B], { fieldName:"continent", operator:"inSet", value:[ "Africa", "Asia", "Australia/Oceania", "Europe", "North America", "South America" ] }[/B] ] }, startRow:0, endRow:80, sortBy:[ "continent" ], textMatchStyle:"exact", resultSet:[ResultSet ID:isc_ResultSet_0 (dataSource: worldDS, created by: filterGrid)], callback:{ caller:[ResultSet ID:isc_ResultSet_0 (dataSource: worldDS, created by: filterGrid)], methodName:"fetchRemoteDataReply" }, willHandleError:true, showPrompt:true, prompt:"Finding Records that match your criteria...", oldValues:{ operator:"and", criteria:[ { fieldName:"continent", operator:"inSet", value:[ "Africa", "Asia", "Australia/Oceania", "Europe", "North America", "South America" ] }, { fieldName:"continent", operator:"inSet", value:[ "Africa", "Asia", "Australia/Oceania", "Europe", "North America", "South America" ] } ] }, requestId:"worldDS$6279", internalClientContext:{ requestIndex:1 }, fallbackToEval:false, lastClientEventThreadCode:"MUP0", bypassCache:true, dataProtocol:"getParams" }
Leave a comment: