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

Community

Connector Improvement: Optional Snake Case when setting up connector

Planned
Rose Craigie User

It would be beneficial to have a configuration option to enable or disable automatic snake casing when setting up a Fivetran connector. Currently, the automatic addition of underscores has created significant work for our team, as we've had to manually remove these unwanted characters from numerous column names. For example, in our source system, column names like 'TEXTVALUE1', 'CUSTOMERID2', and 'TEXT1ISITEMDESCRIPTION' are transformed to 'TEXTVALUE_1', 'CUSTOMERID_2', and 'TEXT_1_ISITEMDESCRIPTION' in the destination. This is not helpful. 

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Egidio Terra Fivetranner

    Hi Rose,

    We’re building a feature that keeps destination names the same as the source. It’s planned for release by the end of the year; we’ll share updates.

     

    Best regards

  • Egidio Terra Fivetranner
    We appreciate you taking the time to share your suggestion! To help us better understand and evaluate your request, could you provide a bit more detail—specifically, which source connectors you’d like us to support?

    We look forward to learning more from your feedback.

    Best regards,
  • Rose Craigie User

    We are migrating our source system (D365 Finance and Operations) from the legacy export-to-datalake process onto Synapse Link for Dataverse, using Fivetran and the Microsoft Dynamics 365 Finance and Operations connector.

    One of the key challenges we’ve encountered is that Fivetran automatically converts column names to snake case. For example, source columns like TEXTVALUE1 are being renamed to TEXTVALUE_1. This behavior is problematic because:

    • Our legacy environment and reports expect the original naming convention.

    • To maintain consistency and avoid breaking reporting when switching sources, we’ve had to add an additional transformation layer that renames columns back to their original form.

    • This introduces unnecessary complexity and effort into our migration.

    It feels presumptuous that the connector enforces this transformation without providing an option to preserve the original names. Having a configuration setting to disable automatic snake casing would make migrations significantly smoother, reduce rework, and allow teams to align column naming directly with their source systems.

    Because this option is not currently available, it makes adopting Fivetran ingestion for D365 FO more difficult than it needs to be.