<@U04SE163WC8> We have a Salesforce Source connect...
# ask-ai
d
@kapa.ai We have a Salesforce Source connector ingesting data from our instance, but are not retrieving all records for the sobjects we configure ie.: Account - with SOQL query over GET
/services/data/v62.0/query
- "totalSize": 9947 Account - with Airbyte sync - 504 records Notable issues on Logs •
Schema validation errors found for stream _Account. Error messages: [$.LastModifiedDate: 2024-10-08T17:38:02.000+0000 is an invalid date-time,...
Source 333e59aa-bc44-4030-8ab6-bcee7a78bb1b has unexpected fields [attributes] in stream _Account
u
Based on the information provided, it seems like there might be a couple of issues at play here. 1. Schema Validation Errors: The error message
Schema validation errors found for stream _Account. Error messages: [$.LastModifiedDate: 2024-10-08T17:38:02.000+0000 is an invalid date-time,...]
suggests that there might be an issue with the date-time format of the
LastModifiedDate
field in your Salesforce data. This could potentially be causing some records to be skipped during the sync process. This issue was also reported in a [Github issue](https://github.com/airbytehq/airbyte/issues/28264) where the user was facing similar schema validation errors. 2. Unexpected Fields: The error message
Source 333e59aa-bc44-4030-8ab6-bcee7a78bb1b has unexpected fields [attributes] in stream _Account
suggests that there might be fields in your Salesforce data that are not expected by the Airbyte Salesforce connector. This could also potentially be causing some records to be skipped during the sync process. To troubleshoot these issues, you might want to consider the following steps: - Check the date-time format: Ensure that the date-time format of the
LastModifiedDate
field in your Salesforce data matches the format expected by the Airbyte Salesforce connector. - Check the schema: Ensure that the schema of your Salesforce data matches the schema expected by the Airbyte Salesforce connector. You might need to adjust the schema of your Salesforce data or configure the Airbyte Salesforce connector to handle the unexpected fields. - Check the sync settings: Ensure that the sync settings of your Airbyte Salesforce connector are correctly configured. For example, if you're using the
Incremental | Append
sync mode, make sure that the
SystemModstamp
field is being used as the cursor field. - Check the Salesforce permissions: Ensure that the user that authenticated to Salesforce has the necessary permissions to access all the fields and records of the Salesforce objects you're trying to sync. If you're still facing issues after trying these steps, you might want to consider creating a Github issue to get further assistance from the Airbyte team.