Amazon App Flow S3 to Salesforce can not select timestamp for incremental transform

Question

my .csv file in S3 has a column CreatedDate in a suitable timestamp / datetime format. When trying to create a flow that incrementally updates the cases at salesforce, I can not select a timestamp column that App Flow then will use to calculate the differences of my file.

The documentation states:
You can also select a source timestamp field to specify how Amazon AppFlow identifies new or changed records. For example, if you have a Created Date timestamp field, choose this to instruct Amazon AppFlow to transfer only newly-created records (and not changed records) since the last successful flow run. The first schedule-triggered flow will pull 30 days of past records at the time of the first flow run.

However I never get prompted to select a timestamp field when creating the flow.

Ryu · Answer

To address the issue, consider the following steps:

Verify the CSV File Schema:
Ensure your CSV file includes a header row and that the “CreatedDate” column is in a standard, recognized timestamp format (for example, ISO 8601 such as “2025-02-09T12:34:56Z”). AppFlow uses schema inference to detect timestamp fields; if the format isn’t recognized, it won’t prompt you to select a source timestamp.

Review Connector Limitations:
Note that incremental sync based on a source timestamp may not be supported for all connectors or file formats. Although the documentation mentions the ability to select a timestamp field, this functionality might be limited to certain connectors (for example, Salesforce or DynamoDB) and may not work with S3 CSV files. Double-check that your AppFlow configuration for S3 supports incremental flows.

Re-import or Manually Configure the Schema:
If your CSV is correctly formatted, try re-importing the schema when creating the flow. In some cases, starting a new flow (or even a new S3 file with a confirmed header and timestamp column) can force AppFlow to detect the “CreatedDate” column as a timestamp field.

Consider Alternative File Formats:
If the CSV approach does not work, you might experiment with converting your file to JSON format, where you can explicitly define the field types. JSON schemas can sometimes provide more control over type recognition in AppFlow.
 
By following these steps, you can help ensure that AppFlow correctly recognizes your timestamp field for incremental updates.

Amazon App Flow S3 to Salesforce can not select timestamp for incremental transform

Add your answer

Relevant content