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

Community

Destination Improvement: Explicit overrides for naming conventions

Answered
Solomon Shorser User

Some of our data contains column names for other tables. The problem is some source tables have columns with names like "Test1" or "Field2Something" and these get automatically transformed to "test_1" and "field_2_something". This makes it difficult to query these columns in the destination because we need to take the underscores into account. 

It would be nice if we could override or disable the underscore part of this naming convention.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Kevin Kim Fivetranner

    Hi Solomon,

    Thank you for your feedback on our feature request portal, I'm Kevin from the product team. As you mentioned, we have default renaming rules within our data platform that automatically get applied to each connector, you can find detailed documentation on it here: https://fivetran.com/docs/getting-started/core-concepts#namingconventions

    While we don't currently have a plan to change these naming conventions, we have heard feedback from many customers about improving how we handle renaming. In fact, we are currently researching a new project to re-evaluate our naming rules to better meet our customers' needs! It's still quite early on, but I will take note of this internally for when we get further into this research, your feedback will be much appreciated.

  • Solomon Shorser User

    Hi Kevin,

    Thanks for your reply! If Fivetran is looking into making changes to renaming, might I suggest another option? If a function were provided that could give us that mapping, that would also work. We use DBT, so if there was a DBT macro/function that could tell us what a column was renamed to, that would be quite useful.

    For example: if "getFiveTranName('Field2Something')" could return "field_2_something", that would be helpful and the need for overriding Fivetran's rules might not be needed.

  • John Min User

    Is there an update on this? I'm running into issues because both table names and field names are having underscores be inserted when not wanted. For example, i'm working with geo data and so I have fields/tables that I want to name h3 or h3_7_agg. But, now, it's ending up as h_3 or h_3_7_agg.