Thanks for this. The pagination url on the API I'm using is only a partial URL, essentially the back half of the original URL query. So I'm struggling to pull the next pages in. My first thought was to store the baseURL as the parameter, then append the initial query to it. Then when pulling the next cursor I append the Next to the baseURL parameter. Not sure how to go about this in the query, though - any ideas?
@@introverted.manager thank you for the recommendation. I was already using relative path, I just couldn't figure out why calling the next cursor wasn't working. Turns out the API is broken 🙃 Not all bad news though, it lead me to your channel that has some great info on it.
Very nicely explained.
Glad to hear!
Thanks for this.
The pagination url on the API I'm using is only a partial URL, essentially the back half of the original URL query. So I'm struggling to pull the next pages in.
My first thought was to store the baseURL as the parameter, then append the initial query to it. Then when pulling the next cursor I append the Next to the baseURL parameter. Not sure how to go about this in the query, though - any ideas?
If I understood correctly, RelativePath function in M might help with that.
I have video about it.
@@introverted.manager thank you for the recommendation. I was already using relative path, I just couldn't figure out why calling the next cursor wasn't working. Turns out the API is broken 🙃
Not all bad news though, it lead me to your channel that has some great info on it.
Glad you were able to narrow it down 😉