Forum Discussion

jhagist's avatar
jhagist
New Contributor III
8 years ago

REST GET: Has Next And Next URL

I can’t find any good documentation on how to set this up. I have reviewed this article and I am still stuck https://www.snaplogic.com/blog/rest-get-and-the-snaplogic-public-apis The json return...
bhupender_singh's avatar
bhupender_singh
New Contributor III
8 years ago

@jhagist
The logic for has next is to evaluate this expression and if it’s true then make a new get request using value in next url field. Assuming your every request gets you 1000 records in one page. So if you have more than 1000 records then you have to make another request by incrementing the page parameter by 1. According to the given example, 369 requests will bring 369000 records. To get the remaining number of records, 397th get request will be required and $entity.get(‘pageSize’) will return 822 records and this condition will fail. I hope this helps.

  1. has next = $entity.get(‘pageSize’) == 1000

  2. next url = “https//secure.p03.eloqua.com/API/rest/2.0/data/accounts?count=1000&page=” + str(snap.out.totalCount+2)

  • robert_parks's avatar
    robert_parks
    New Contributor III
    8 years ago

    @jhagist & @bhupender.singh

    Hi James and Bhupender,

    James – were you able to get this to work?
    We are running into the same situation.
    Can you confirm that the “has next” can take values that were returned by the initial get?

    Our api returns entity.pageNumber & entity.totalPages. Our thought was to have this for the “has next”:
    $entity.pagerNumber < $entity.totalPages.

    This should be valid, right?

    Also, for the next url we were going to use “$entity.pageNumber + 1” to set the page requirement. Is this valid?

    Any direction you can provide would be great. I’ll provide some screen shots if needed.
    Thanks!

    Bob