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

Community

Connector Improvement: Expose all schema tables and provide the ability to select specific tables when configuring the SDK connector.

Answered
Rakshya S User

Description:
Currently, the SDK connector does not provide the capability to expose or select newly added schema tables, nor does it allow refreshing existing tables for historical sync. All table definitions must be hardcoded during the initial connector build, and any new table or historical re-sync requires additional development effort.

This requirement is to expose all available schema tables through the SDK connector, allow the Arbonne data team to selectively choose which tables to ingest, and enable refreshing existing tables for historical synchronization as needed. These capabilities will provide greater flexibility, reduce ongoing dependency on services for schema and data changes, improve scalability, and support faster onboarding of new data sources and evolving business use cases.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Alison Fivetranner
    • Edited

    Hi Rakshya,

    This feature is not currently on our roadmap as the Connector SDK is optimized for Customers to build their own targeted Custom Connections. The Dashboard can be used to resync a complete Connector SDK connection using the Resync all historical data button from the Setup page. If the state object has been appropriately designed it is possible to re-sync one or two specific tables by using the Fivetran API to directly manage the connections state object (docs available here). The connector SDK system can infer new tables and columns whenever they appear so you don't have to 'hardcode all table definitions'.

    I would like to better understand the use case you have that is leading to this request?

    Part of building a custom connection is identifying the data that is needed and focusing the development effort just on that data. Requiring all tables to be built out and fully tested just so you can turn some of them off seems like it would slow the development effort down rather than speed it up.

    Thanks,
    Alison