$skip OData query parameter not working

[Brad Warman]

Hi everyone. I am attempting to paginate a REST GET call to SAP due to a hard coded restriction of the number of items returned in a payload. I can successfully use the OData $top query parameter to reduce the number of items returned if required, but whenever I add $skip to assist in pagination, the request always fails. I've tried using $skip in conjunction with $top as well as on it's own, in both scripted REST calls and in a flow, but every time it's added, the request fails.

Any ideas on what could be causing this? Using $skip in postman hitting the same endpoint works as expected.

Cheers,

Brad

[palanikumar]

Hi,

Did you try calling this API from PostMan? Since you are getting response in HTML format, check whether the URL you are using is correct. 

[Brad Warman · Accepted solution]

Hi @palanikumar. Yeah it works perfectly in Postman. Given the critical nature of the request, I ended up just splitting the call into two parts - one for active records and one for inactive. It took a lot of trial and error but I eventually found a way to use $filter in a way that ServiceNow allowed. This gets us well under the hard coded 5000 record limit on both calls and allows us to obtain all the data we need.

There seemed to be a few OData queries that just wouldn't work when sending from ServiceNow, $skip being one of those. Interestingly, $count is also not working.

Thanks for your help with this though.