Rest API @odata.nextLink disappears when I apply a $filter ?

Copper Contributor

I am building a pipeline from a Rest api, if I run the request I get the @odata.nextLink so can apply pagination OK.


If I apply a $filter this @odata.nextLink disappears from the Body so cannot apply pagination any idea's ?


No Filter Applied


 No Filter.png

With filter I lose the @odata.nextLink pagination information


With Filter.png

1 Reply
Hi Calex,
Seems the API has a default page size set to 1000.

If there is only one page of response, then certainly the pagination will be skipped.

I bet if you change the filter to 'id lt 1002' and you will see the pagination link pop again.

However, I am curious what's the real problem here that troubles you, without this pagination prop?