Change Data Capture Developer Guide

Change Data Capture
Keep Your External Data Current with Change Data Capture
Subscribe to Change Events
Change Event Message Structure
Security Considerations
Change Event Considerations
General Considerations
Change Event Allocations
Standard Object Notes
Sending Data Differences for Fields of Updated Records
Other Types of Change Events: Gap and Overflow Events
PDF

Newer Version Available

This content describes an older version of this product. View Latest

General Considerations

No Change Events Generated for Some Actions
The following actions don’t generate change events.
  • Renaming a picklist value, including renaming an opportunity contact role (OpportunityContactRole object)
  • Deleting a picklist value
  • Updating a default picklist value
  • Changing the data type of a custom field
No Apex Trigger Support
Apex triggers aren’t supported for subscribing to change events.
Field Support
  • Formula fields aren't included in change events.
  • Known Issue: If a standard object contains more than 20 custom fields, change events might not include all custom field changes. Change events still include updated standard fields. The issue occurs even after deleting custom fields to bring the total number of fields below 20. This issue is limited to standard objects in API version 44.0, doesn’t apply to custom objects, and is fixed in the next release.
Geolocation Compound Fields
When a geolocation compound field (of type location) is changed in a custom object, all its component fields are published in the change event whether they were changed or not. In contrast, when a geolocation field is changed in a standard object, only the changed field is published. For more information, see Geolocation Compound Field in the SOAP API Developer Guide.