You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A developer outlined his workflow to get the latest changes from a sync:
When I receive a webhook for a triggered sync, I'm using getRecords to pull the data into our data model. The way I'm thinking to go about this to support successive syncs is to check if the sync type is INITIAL , if it is I don't add a delta to the getRecords call but if it's not the initial sync I will add the queryTimestamp to the getRecords delta field
To further simplified this logic, we can avoid sending a timestamp when the sync is INITIAL. That way, developers don't even need to check if syncs are INITIAL or not, and can just use the timestamp.
The text was updated successfully, but these errors were encountered:
* [gh-#975] move data related services to its own directory
* [gh-#975] fix remaining reference
* [gh-#975] remove queryTimeStamp if sync is initial
Resolves#994
* [gh-#975] deleted property isn't optional
* [gh-#975] add nango_metadata property to all results
* [gh-#975] add metadata
* [gh-#975] test fixing and type improvements
* [gh-#975] fix tests and extract record property
* [gh-#975] types update
* [gh-#975] docs update
* [gh-#975] null for queryTimeStamp
A developer outlined his workflow to get the latest changes from a sync:
To further simplified this logic, we can avoid sending a timestamp when the sync is
INITIAL
. That way, developers don't even need to check if syncs areINITIAL
or not, and can just use the timestamp.The text was updated successfully, but these errors were encountered: