Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Destination Improvement: Create Tables Even if there is No Data

Answered
Blake Nelson User

Currently, when a connection doesn't find data in a table, it simply skips the creation of that table in the destination.  

If the processes that are triggered afterward are expecting data from those tables, they will fail.  

We would request that if data is not found, the table still be created in the destination and left empty.  This confirms that the field was there but without data and makes for smoother handling of the data schema by subsequent systems.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Egidio Terra Fivetranner
    • Edited

    Hi Blake,

    Thanks for your request around creating a new table even when no data is available — that’s really helpful context.

    To better understand your use case, could you share a bit more about your workflow? Specifically:

    • What connectors are you using?
    • At what point in your pipeline you expect the table to be created (e.g., initial sync, incremental updates)?
    • How you plan to use the table downstream (e.g., for modeling, BI, or orchestration)?

    Any additional details will help us evaluate the best approach here.

    Appreciate your help!