Transformations: Rename fields in case of a conflict in the destination
Completed
It would be good to be able to rename fields in the case of the conflict in the destination, so the source does not need to be modified. For example, Redshift has a reserved word "oid" that cannot exist on the source, or an error occurs.
-
Official comment
Hi Phillip,
This feature—avoid name conflict in the destination—is now live and generally available for database connectors. You can configure the connector to use its name at the destination, thus avoiding conflicts. Documentation and release notes for this functionality are available in the Fivetran documentation
Thank you to all who provided feedback and for your patience.
Best regards,
-
Hey Phillip, thanks for reaching out regarding this! Do you mind elaborating on a specific experience where this is occurring for you?
Please sign in to leave a comment.
Comments
2 comments