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

Community

Feature Request: Synchronize Field Names and Data Types Between HVR and Fivetran SaaS

Answered
Himanshu Jain User
  • Edited

Dear Fivetran Product Team,

We are writing to request a feature enhancement for better compatibility between HVR and Fivetran SaaS platform. 

Issue:
Currently, there are inconsistencies in field naming and data types field generated for all tables created by between HVR and Fivetran SaaS

Specific Field Mismatches:

1. Sync Timestamp Fields:
   - HVR: hvr_last_upd_time (TIMESTAMPTZ)
   - Fivetran: _fivetran_synced (TIMESTAMP_TZ)

2. Deletion Flag Fields:
   - HVR: hvr_is_deleted (NUMBER(30))
   - Fivetran: _fivetran_deleted (BOOLEAN)

Feature Request:
We request Fivetran to provide an option to synchronize field names and data types between HVR and SaaS platforms:

1. Field Name Alignment: Option to use consistent naming convention (either HVR or Fivetran SaaS )
2. Data Type Consistency: Ensure matching data types for equivalent fields across both platforms
3. Configuration Setting: Allow users to choose their preferred naming/typing convention during setup

 

Business Impact:
- Reduces complexity in data pipeline development
- Improves data consistency across platforms
- Simplifies migration between HVR and SaaS solutions
- Reduces maintenance overhead for dual-platform environments

This enhancement would significantly improve our data integration experience and reduce operational complexity.

Please let us know if you need additional details or would like to discuss this request further.

 

Reference:

 

 

 

Please sign in to leave a comment.

Comments

4 comments

Date Votes
  • Mark Van de Wiel User

    Himanshu,

    I agree that compatibility would be useful.

    If we gave you the option to make the additional HVR fields identical in name and data type to the Fivetran fields, would that solve your concern?

    I am a bit worried about the source to destination data type mapping as these may be subtlety different as well. To synchronize these would be tricky.

    Thank you,
    Mark.

  • Himanshu Jain User

    Hi Mark,

    Thank you for your response and for considering our feature request.

    Yes, having the option to make HVR fields identical in name and data type to that of Fivetran fields would solve our concern and have consistency in the system-generated fields (sync timestamps and deletion flags) rather than the source data fields themselves.

    This would enable us to use the same downstream processing logic for both HVR and SaaS data and build unified KPI dashboards without field mapping complexity thereby simplifying our data harmonization efforts significantly.

    Best regards,
    Himanshu Jain

  • Mark Van de Wiel User

    ok. Let me see if we can get a project for this on the planning for our next quarter (that starts in November).

    Thanks,
    Mark.

  • Mark Van de Wiel User

    Himanshu,

    Please do note that in HVR you can change the names and data type of the extra columns.

    Names can be changed either as part of the create channel flow, or after creating the channel as part of the channel actions. The channel action is also where you change the data type for the soft delete flag.

    I ran a quick test to get HVR names and data types in sync with Fivetran which works.

    All of that said we can make this a lot easier than it currently is. So I will follow up with this.

    Thanks,
    Mark.