ZohoCRM connector appends new data on incremental deduped mode instead of updating

Hello everyone, I’m experiencing sync issues with the ZohoCRM connector.
Any help will be appreciated, thanks!

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: 20.04.1-Ubuntu
  • Memory / Disk: unlimited
  • Deployment: Docker
  • Airbyte Version: 0.36.3-alpha
  • Source name/version: ZohoCRM:0.1.0
  • Destination name/version: Postgres:0.3.18
  • Step: Sync issue
  • Description: Remove this with the description of your problem.

Current Behavior:
When a lead is modified it is appended in the DB.

Expected Behavior:
The record should be updated with the new data.

Steps to Reproduce

  1. Create a connection between Zoho → Postgres
  2. Replicate the contacts and leads table using airbyte incremental deduped mode
  3. Make changes in the CRM
  4. Sync
  5. Watch the new changes append instead of updating the current ones

logs:

.incremental_leads_zoho_crm_stream=incremental - append_dedup, null

WriteConfig{streamName=airbyte_incremental_leads_zoho_crm_stream, namespace=null, outputSchemaName=public, tmpTableName=_airbyte_tmp_ngr_airbyte_incremental_leads_zoho_crm_stream, outputTableName=_airbyte_raw_airbyte_incremental_leads_zoho_crm_stream, syncMode=append_dedup}

2022-06-27 06:51:55 e[43mdestinatione[0m > 2022-06-27 06:51:55 e[32mINFOe[m i.a.i.d.j.JdbcBufferedConsumerFactory(lambda$onStartFunction$1):126 - Preparing tmp table in destination started for stream airbyte_incremental_leads_zoho_crm_stream. schema: public, tmp table name: _airbyte_tmp_ngr_airbyte_incremental_leads_zoho_crm_stream

2022-06-27 06:52:01 e[44msourcee[0m > Syncing stream: incremental_leads_zoho_crm_stream
2022-06-27 06:52:01 e[44msourcee[0m > Setting state of incremental_leads_zoho_crm_stream stream to {'Modified_Time': '2022-06-27T08:51:05+03:00'}
2022-06-27 06:52:03 e[44msourcee[0m > Read 464 records from incremental_leads_zoho_crm_stream stream
2022-06-27 06:52:03 e[44msourcee[0m > Finished syncing incremental_leads_zoho_crm_stream
Syncing stream incremental_leads_zoho_crm_stream 0:00:01.739624 (x? many times)

2022-06-27 06:52:07 e[43mdestinatione[0m > 2022-06-27 06:52:07 e[32mINFOe[m i.a.i.d.r.InMemoryRecordBufferingStrategy(lambda$flushAll$1):84 - Flushing airbyte_incremental_leads_zoho_crm_stream: 464 records (6 MB)

2022-06-27 06:52:08 e[43mdestinatione[0m > 2022-06-27 06:52:08 e[32mINFOe[m i.a.i.d.j.JdbcBufferedConsumerFactory(lambda$onCloseFunction$3):166 - Finalizing stream airbyte_incremental_leads_zoho_crm_stream. schema public, tmp table _airbyte_tmp_ngr_airbyte_incremental_leads_zoho_crm_stream, final table _airbyte_raw_airbyte_incremental_leads_zoho_crm_stream

2022-06-27 06:52:11 e[43mdestinatione[0m > 2022-06-27 06:52:11 e[32mINFOe[m i.a.i.d.j.JdbcBufferedConsumerFactory(lambda$onCloseFunction$3):188 - Cleaning tmp table in destination started for stream airbyte_incremental_leads_zoho_crm_stream. schema public, tmp table name: _airbyte_tmp_ngr_airbyte_incremental_leads_zoho_crm_stream

"incremental_leads_zoho_crm_stream":{"Modified_Time":"2022-06-27T09:51:31+03:00"},

.StreamSyncStats@2453216c[streamName=airbyte_incremental_leads_zoho_crm_stream,stats=io.airbyte.config.SyncStats@4326410[recordsEmitted=464,bytesEmitted=1406198,stateMessagesEmitted=<null>,recordsCommitted=464]],


2022-06-27 06:52:11 e[32mINFOe[m i.a.w.DefaultReplicationWorker(run):254 - State capture: Updated state to:
...
"incremental_leads_zoho_crm_stream":{"Modified_Time":"2022-06-27T09:51:31+03:00"},
.StreamSyncStats@2453216c[streamName=airbyte_incremental_leads_zoho_crm_stream,stats=io.airbyte.config.SyncStats@4326410[recordsEmitted=464,bytesEmitted=1406198,stateMessagesEmitted=<null>,recordsCommitted=464]]

"incremental_leads_zoho_crm_stream":{"Modified_Time":"2022-06-27T09:51:31+03:00"},





This is an expected behavior.

we can close the thread

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.