Hello All,
Has somebody previously used Search-After pagination method in a custom flow?
If yes could you please provide a little insight of the setup.
Thanks
@yashkumar is there a specific endpoint with documentation that you're thinking about?
@tylerlamparter Yes, Here's the link to the endpoint Documentation.
@yashkumar it looks like you would just use the "next page url" option in IO. From the docs, they respond with a next url link that has the search_after parameter already filled for you.
@tylerlamparter This configuration is something which we are already using .
Well here's the confusing part, is the "Search after pagination" same as "Next page URL"?
Current configuration i.e "Next page URL" works fine for smaller number of records.
But the moment we try to perform the bulk import it throws the error in the screengrab below.
This is what lead to the conflict that is Search after is different from "Next Page url"!
@yashkumar what does the rest of your setup look like? What do you have in the relative url section of the export setup?
Everyone's terms for paging vary, but in this case, we use next page url because they are returning you a full url to use to grab the next page. Within that url, it specifies the page mechanism. Based on their docs, it says to use the _links to get the next page as you can't explicitly come up with the query parameter on your own.
@tylerlamparter Here's the complete export setup:-
GET- Call
api/rest/v1/product-models?search={"updated":[{"operator":">","value": "{{lastExportDateTime}}"}]}
@yashkumar this is interesting because the next link url we're using clearly has paging method as search after. Can you debug that export step and review the requests being sent out?
