Connector Improvement: Epic Clarity Connector: keep 'Destination schema prefix' when 'Source naming' is selected
PlannedCurrently, when you select 'Source naming' for the Epic Clarity Connector, the 'Destination schema prefix' is ignored. We want to option to keep it, but withouth using the 'Fivetran naming' option.
Example: we want our schema like this: "epic_clarity_56_dbo"
Currently, we get this: "dbo"
Since dbo is a common SQL Server schema, we could end up mixing tables from different databases into the same 'dbo' schema.
See this ticket for more details on our specific case:
https://support.fivetran.com/hc/en-us/requests/286073
-
Official comment
Hi Paul,
Thanks for your comment in our feature request portal!
We are currently working on a feature to allow customers to give custom names to schemas, columns, and tables. Once this is available, you'll be able to specify the exact schema name for each connector / schema / table / column that you are syncing!
I don't have an exact timeline yet but we're currently planning this so please stay tuned!
Please sign in to leave a comment.
Comments
1 comment