Skip to main content

Connector Improvement: Option for Using a Primary Key in File Connectors to MERGE data

Answered

Comments

2 comments

  • Official comment
    Kevin

    Hi John and Britt,

    Thanks for your comments here! It is definitely not ideal to have duplicate rows or too many tables in your destination warehouse.

    We can investigate a few possible solutions to this, I wonder if we can either improve how we infer the PK, or as mentioned, allow users to specify it directly (possibly either in the file or via the UI).

    However, minimum configuration is one of our key principles, so while we discuss this internally, we want to keep the best user experience in mind. I understand this is causing a pain point and we will look into this to provide the best solution for our users.

    Please let me know if you have further comments or questions!

  • Britt

    Strongly agree with John. Understand that no primary key probably proves challenging to create the connector but I have otherwise found this Box connector not helpful. 

    This would have been an awesome solution for my company, since we receive data from 3rd parties via csv (automated) and have since had to insert manually which is a huge cost on resources over time that could be utilized doing something more productive than inserting data. And, for better or worse, we send 3rd party vendors without an API (or something else) to Box to get us close to a somewhat automated solution.

    Point is, this was so close from relieving us from a very painful and menial task - and was surprised to see upon connecting 100s of separate tables dropped in our warehouse. 

    0

Please sign in to leave a comment.