Connector Improvement: Enhance the Incremental sync logic for CONTACT_TRANSACTION
AnsweredTopic 1: Missing transactions in CONTACT_TRANSACTION:
Problem :
Option 1 (All transactions associated to the Contact are extracted every time): when transactions are added/updated, the last modified date of the corresponding contact record is not updated, so the connector is not able to fetch the transactions for that contact. So only when the contact record is added/updated, do we sync transactions for that contact.
Proposed approach : Incremental data from directory_contact table
+. ( Add on process)
Distribution_contact has the contact_id.
Get the Contact_IDs incrementally from DISTRIBUTION_CONTACT/DISTRIBUTION and fetch transactions for that contact.
Option 2 ( Optimal approach : Extracts only Incremental Transaction IDs) : Currently Contact Transaction is referring DIRECTORY CONTACT (Contact ID) for incremental data extraction, which is pulling unnecessary data (All transactions for a given contact ID)
Distribution contact/ distribution(request type=’Invite’) has contact transaction ID, if we use these contact transaction IDs for incremental data extraction, then the data volume will be reduced.
-
Official comment
Hi Sriman,
Thanks for raising this. This is a known source limitation with Qualtrics and something we are actively discussing with them.
In the meantime, we do have a feature that allows you to select a specific directory, which should help improve sync performance. Have you tried enabling that? If so, are you still seeing performance issues?
We will continue to follow up with Qualtrics and try to get this expedited on their end.
Thanks,
Vignesh
Please sign in to leave a comment.
Comments
1 comment