Skip to main content
To homepage To homepage
Solved

REST API pagination limit offset

  • April 18, 2026
  • 3 replies
  • 25 views
D
Starter

Hi, 

I'm trying to consume REST API with limit/offset pagination

https://<>.rest.afas.online/ProfitRestServices/connectors/<connector>?skip=250&take=250&orderbyfieldids=Medewerker

skip = Offset. in the example above skip the first 250 rows 

take = limit. take 250 rows
 

seems to work in Postman
 


My approach was to use 'override pagination’



In combination with endpoint's 'query parameters’
 

 using the following expression:

SELECT ({TX_NextPage}  - 1) * 150 AS skipValue

When running the ODX tasks it seems to ingest only the first page. 

What am i'm doing wrong?

 

Best answer by rory.smith

Hi,

did you already have a look here: Connecting to AFAS with the TX REST Connector | Community ? I usually turn on debug logging and file caching for the endpoint I am working on to see if that shows me anything going wrong, the debug logging shows you the values of variables before each call for instance.

3 replies

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • rory.smith
  • TimeXtender Xpert
  • Answer
  • April 20, 2026

Hi,

did you already have a look here: Connecting to AFAS with the TX REST Connector | Community ? I usually turn on debug logging and file caching for the endpoint I am working on to see if that shows me anything going wrong, the debug logging shows you the values of variables before each call for instance.

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • April 20, 2026

Hi ​@Dror.Svartzman_1 

In my guide.

I have many examples. I don’t see why using that expression is necessary when you can use TX_CurrentPage instead.

D
Starter

Hi Rory, 

Thank you. This article was extremely helpful! 

Just out of curiacity where can set the debug logging and file caching. 

​@Thomas Lind  following the guide andrew.gebhard, i've used pagination on datasource level which seems to do the trick!

 

Terms and ConditionsAccessibility statement