Fun with SearchService.quickSearch Pagination

[RobertCalise]

When utilizing SearchService.QuickSearch, results are not properly paginated. In this case, I'm using the PHP SDK:

$api->quickSearch('FindPerson', 1, '', 0, 25); returns 25 results, as expected.

However:
$api->quickSearch('FindPerson', 1, '', 1, 25); returns 50 results.
$api->quickSearch('FindPerson', 1, '', 2, 25); returns 75 results.
$api->quickSearch('FindPerson', 1, '', 3, 25); returns 100 results.
$api->quickSearch('FindPerson', 1, '', 4, 25); returns 125 results.

The expected behavior here is that each call would consistently return the next page of 25 results. What it seems like is happening instead is that it's returning ($limit+1)*$page results, which is really strange.

Additionally, the published maximum number of results that can be returned is 1,000, but here's what happened in another test:

$api->quickSearch('FindPerson', 1, '', 125, 25); returns 3,150 records

Which means that ($limit+1)*$page isn't accurate, so I'm really not sure what's happening on the backend here.

I've opened a support case about this, but was wondering if anyone else has run into this same issue? Justin, are you able to shed some light here?

[JoshMoore]

Sorry for the long response time on this. Pav pointed it out to me.

I have created the bug ticket.

[RobertCalise]

Thanks, Josh!

[JoshMoore]

Looks like dev fixed the issue, the proposed fix will go to QA then it should be released in a maintenance patch.