Connector Improvement: Current FiveTran connector replication data from SalesForce source implicitly transform table/column names, causing data loss
CompletedFiveTran replication when on Salesforce data, automatically transform source table with columns using internal FiveTran defined rule sets and create tables with columns at customer target with names transformed.
This is causing the data loss on following situations on SalesForce as data source:
1) if multiple fields (columns) exist with different forms of names, such as Employee_Change_in_StatusAllowed__c and Employee_Change_in_Status_Allowed__c (this is a live example from our 'lead' SF table) FiveTran detects them as duplicates and pick one to replicate while ignore another. In our live example, FiveTran picks column with older data so we don't get the the newer data from another column. This is causing the data loss. Similar situation could also exist if source if case-sensitivity is enforced at the source and multiple columns with the same name but different cases in place that would also cause FiveTran's treatment as 'duplicates'.
-
Official comment
Hi Joe,
Thanks for reaching out about this. The good new is, we have a solution for you! Please file a ticket with our Support team asking to be added to our feature flag that applies different renaming rules for Salesforce. You can mention my name in the ticket if they have any questions.
Best,
Sadie
Please sign in to leave a comment.
Comments
1 comment