Connector Improvement: SFDC Connector schema management API does not enable or disable schemas
Answered
There are duplicated fields at source, and fivetran will arbitrarily choose one over the other. There is no way to distinguish or change what is chosen. The connector schema management API returns identical results.
There is already severe limitations on Fivetran behavior. And the programmatic management is pretty useless.
"subscriptionStartDate__c": {
"name_in_destination": "subscription_start_date_c",
"enabled": true,
"hashed": false,
"enabled_patch_settings": {
"allowed": true
},
"is_primary_key": false
},
"Subscription_Start_Date__c": {
"name_in_destination": "subscription_start_date_c",
"enabled": true,
"hashed": false,
"enabled_patch_settings": {
"allowed": true
},
"is_primary_key": false
},
-
Official comment
Hi Christina,
Sadie from the Product team here. I believe you're seeing this behavior due to our standard table and column naming conventions, which make the field names in your example above the same. We can override this behavior for you, which would mean the fields are no longer considered duplicates. If you're interested in this, please reach out to our support team and ask them to be added to the feature flag for Salesforce renaming. You can reference this message and have them reach out to me if they have any questions.
Best,
Sadie
Please sign in to leave a comment.
Comments
1 comment