Limitations and considerations

The following limitations apply when using Salesforce as a source in a Replicate task:

• Object types limitations:
  • External objects are not supported as they cannot be queried.

  • Big objects are supported using Full Load replication only. If you want to replicate updates to Big Objects, you will need to schedule your task - which must be configured with Full Load replication - according to the expected update frequency.

    For information on scheduling tasks, see Scheduling jobs.

• DDLs are not supported.
• The "Estimated Count" in the Full Load monitoring statistics will be N/A.
• Only the user + password + security token authentication method is supported
• Shield Platform Encryption is not supported.
• The source_lookup Data Enrichment function is not supported. For more information on this function, see Data Enrichment functions
• The AR_H_USER header column is not supported. For information on using header columns, see Headers.
• When storing changes in Change Tables, the before-image will not be stored.

• Replication of tables without tracking columns (for example, lastModifiedDate) is supported in Full Load only tasks.

• Some tables can only be replicated by using a Replicate filter.

  Example:

  select. * from vote is not supported

  select * from vote where account_id=1234 is supported

  For more information, see https://developer.salesforce.com/docs/atlas.en-us.200.0.object_reference.meta/object_reference/sforce_api_objects_vote.htm

• The transaction ID displayed in the AR_H_TRANSACTION_ID header column will be a Replicate-generated ID, and not the original Salesforce ID (txn_id).
• Replicating data that has been recovered from the Recycle Bin (Undelete) will be shown as an UPDATE operation in the Change Processing tab in the Monitor view. To prevent this, set the Apply Conflicts error handling for UPDATEs to: No record found for applying an UPDATE: INSERT the missing target record .
• Compound fields are fully supported using SOAP API only. Therefore, if you need to replicate such fields, it is recommended to choose SOAP API as your Full Load/CDC method in the Advanced tab. If you do choose Bulk API, the underlying fields will be replicated as separate columns instead only without the additional compound field.
• As the data is captured directly from Salesforce tables, a sequence of operations might be merged into a single operation. For example, an INSERT followed by UPDATEs to the same record in the same capture cycle will be handled as an INSERT.
• Replication of CDP (Customer Data Platform) objects is not supported.

• Replicating data with 4-byte emoji characters is not supported.