Closed dkarkanas closed 8 months ago
@dkarkanas so, when calling:
var result = await myCasePartialQueryable.ToResultSetAsync(options);
options.Size
will have a default value of 100, if no other value is provided from calling side.
If a value (e.g. 1) is provided, the data case filtering (why are we doing this particular filtering after the query?) fails because it is applied on a "wrongly created" list (result
).
The only reason we hadn't experienced this issue before is the fact that no user had >100 cases (or no client specified a small Size...).
When a case data filter was applied (e.g.,
data.someId::eq::(string)123ABC
) to the GetMyCases endpoint, we executed the results first and then applied the filtering.This led to issues with pagination since we had a default of 100 all this time, and we were unaware of it.