Incremental Sync for Non-Timestamp Fields

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

User inquires about the possibility of enabling incremental sync on non-timestamp fields using the UI builder for APIs like Microsoft Graph that support delta sync functionality.


Question

Hey all,
I’m trying to understand if theres an ability in the UI builder (or upcoming ability maybe?) to enable incremental sync on a field which is not a timestamp. Just a string. For api’s like microsoft graph /users which have an additional api /users/delta which can be incrementally synced using a deltatoken we got from the previous sync.
Anyone aware of a way or a hack or we must use CDK for such cases?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

['incremental-sync', 'ui-builder', 'microsoft-graph', 'users', 'deltatoken']
2

The delta token looks more a pagination cursor than incremental. Incremental syncs are to retrieve records were updated and you want to keep them updated with your source. How would you get updated records using the string-cursor?

3

I see what you saying, but isn’t the pagination relevant for next pages? i need to store the delta token and use it in the next sync so it will continue from there

4

No, pagination is related to query and ingest all data available in the source service. If you can’t finish reading all the data you’re going to ended up with partial data and it’s a problem.