If you use the Bulk v1 API you cannot extract compound fields. You must exclude them from your list of ingested fields.
"CRITICAL Error syncing ContactPointAddress: InvalidBatch : Failed to process query: FUNCTIONALITY_NOT_ENABLED: Selecting compound data not supported in Bulk Query", "level": "info", "timestamp": "2023-08-02T10:03:30.226398Z"}
I believe Compound fields could be automatically excluded by doing a look-up first against the Salesforce Data Dictionary and examining for the given table being ingested whether any of the columns are compound fields e.g. "compoundFieldName": "Coordinates__c", . In the example provided, the compound field Coordinates__c should be excluded when using a Bulk API method.
To find out more about the Salesforce Data Dictionary and dumping the Data Dictionary look at this github repo https://github.com/s7clarke10/get-salesforce-data-dictionary.
If you use the Bulk v1 API you cannot extract compound fields. You must exclude them from your list of ingested fields.
"CRITICAL Error syncing ContactPointAddress: InvalidBatch : Failed to process query: FUNCTIONALITY_NOT_ENABLED: Selecting compound data not supported in Bulk Query", "level": "info", "timestamp": "2023-08-02T10:03:30.226398Z"}I believe Compound fields could be automatically excluded by doing a look-up first against the Salesforce Data Dictionary and examining for the given table being ingested whether any of the columns are compound fields e.g.
"compoundFieldName": "Coordinates__c",. In the example provided, the compound fieldCoordinates__cshould be excluded when using a Bulk API method.To find out more about the Salesforce Data Dictionary and dumping the Data Dictionary look at this github repo https://github.com/s7clarke10/get-salesforce-data-dictionary.