Connector Improvement: Allow User-Specified Uniqueness Columns
Answered
Our PeopleSoft databases (running on Oracle RAC) have tables with multiple column unique keys and no single primary key field. I would like the ability to specify in Fivetran what columns make up the uniqueness so when the data comes in, it can accurately identify which records have changed.
We have a situation where one of the tables has what we consider duplicate rows due to the uniqueness fields but when a different field was updated, Fivetran pulled it in as a brand new record (different _fivetran_id) and so now I have two records where there should only be one. We're working with support to resolve this, but still think this would be a helpful addition.
-
Official comment
Hi Phyllis,
Thanks for your feedback in our feature request portal!
I agree that we should also leverage unique keys and treat them as primary keys for Fivetran syncs, instead of syncing them as primary key-less tables. I have filed this ticket over to our engineering team and we will evaluate this with other priorities. This should not be a major lift, so I believe we should be able to address this relatively soon. While I don't have a clear timeframe at the moment, please stay tuned on this thread for more updates!
Please sign in to leave a comment.
Comments
1 comment