Hi Matthew H.
Has Next โ keep it exactly as is, it's correct:
$.entity.meta.page.hasMore == true
Next URL โ need to construct the next URL using from or to as a cursor. The pattern is usually:
"https://their-api-base-url.com/their/endpoint?from=" + $.entity.meta.page.to
The to value (2279) typically becomes the starting point for the next page โ the API is likely paginating backwards through record IDs.
To answer your direct question: No, do NOT replace the Has Next line. Keep it. Just add the Next URL field with the constructed URL above.
---
To confirm the exact cursor field, should check your API docs โ specifically whether the next page call uses from=<to_value> or cursor=<to_value> or something else. But the $.entity.meta.page.to value is almost certainly the right cursor to use.
"What does the base URL of your API call look like, and is there a from or cursor query parameter?" โ that'll confirm the Next URL expression pattern. ๐