I have on-premise deployment and using connector builder for servinow API. Want to follow this advice, but how to 2 queries and get last_sys_id from previous query like this? "A workaround is to NOT use sysparm_offset. Instead, order your results by sys_id (which you are already doing) and add an additional clause to your sysparm_query as follows: sys_id>_{last_sys_id}_ where _{last_sys_id}_ is the maximum sys_id value from the previous query."

I'm sorry, but the knowledge sources provided do not contain specific information on how to implement the workaround you mentioned for the ServiceNow API using the Airbyte Connector Builder. However, the Connector Builder does support pagination methods, which can be used to fetch consecutive pages of data from an API. If the ServiceNow API supports pagination, you can configure this in the Pagination section of the Connector Builder. For example, some APIs use offset and limit values as query parameters, while others use cursor pagination, which includes tokens or links to subsequent pages of results in its responses. For more detailed instructions on how to use the Connector Builder, including how to connect to an API and extract records from the response, you can refer to the [Airbyte documentation](https://docs.airbyte.com/connector-development/connector-builder-ui/overview). If you need further assistance, I would recommend reaching out to the Airbyte community or support for more specific guidance.

@kapa.ai connector builder does NOT allow saving output of fields and getting MAXIMUM value of 1 column/field to be used in next pagination query?

Based on the provided knowledge sources, it appears that the Connector Builder in Airbyte currently supports common pagination methods used by APIs, such as limit-offset and page count. However, there is no explicit mention of the ability to save the output of fields or get the maximum value of a column/field to be used in the next pagination query. In the Pagination section of the Connector Builder, you can provide a configuration to request consecutive pages of data from the API until there are no more pages to fetch. If your API doesn't support pagination, you can leave this section disabled [source](https://docs.airbyte.com/connector-development/connector-builder-ui/pagination). However, there are discussions and open issues on GitHub that suggest users have faced challenges with pagination, especially when dealing with nested fields or specific pagination tokens [source](https://github.com/airbytehq/airbyte/discussions/44913), [source](https://github.com/airbytehq/airbyte/issues/40697). For more specific capabilities or to address particular issues, it might be best to refer to the official Airbyte documentation or engage with the Airbyte community on GitHub.