Thomas, I'll log this as a bug as I was able to reproduce. Unfortunately, it looks like when specifying the IDs in the manner, that it throws off the logic to show/hide the next link. The appearance of the "next" navigation is how you know if there are more rows to fetch, and the URL it is providing most certainly is not correct.
Wish I had a better answer for you, but I've gone ahead and filed the issue.
JIVE-48002 - Invalid API "next" Link for People Service When Using ids Filter
Thank you for the answer.
I guess I will find all the API bugs this month! Isn't there are cash reward for bug finding ?
In this case, I will have to count the number of request and handle the pagination beforehand.
This isn't too bad I guess. My real worry is the other API but where the pagination does not return all the results ( case 344383)
I just escalated that case and really hope that Jive will be able to help on that bug.
Ask and you shall receive. Check your Gamification Profile, you should have a nifty new badge. =) Also, I've nudged the ticket on the above case thread and it should be fixed in our next cloud release.
1 person found this helpful
Haha , thank you I 've displayed it proudly.
For the bug, the support team found me a workaround : for followers export, you can set the count variable to 1000. This is not always the case, but here it's possible. So for now I'm no longer blocked.