Skip to main content

Community

Connector Improvement: _fivetran_synced column for history

Please sign in to leave a comment.

Comments

1 comment

  • Official comment

    Hi Ramesh,

    Thanks for your post here!

    In history mode, we update the _fivetran_end column to when the record was made inactive. Would this address your use case?

    When a record is updated in the source, in history mode the previous version will have it's _fivetran_end column set to the time of the new version's update, and the new version will have a new _fivetran_start timestamp.