ExtlRecShrEvent

Tracks the record data published from a vendor’s Salesforce org to a connected partner’s org for Partner Connect. This object is available in API version 62.0 and later.

Supported Calls 

describeSObjects()

Supported Subscribers 

SubscriberSupported?
Apex Triggers 
Flows 
Processes 
Pub/Sub APIYes
Streaming API (CometD)Yes

Subscription Channel 

/event/ExtlRecShrEvent

Event Delivery Allocation Enforced 

No

Special Access Rules 

To see this object, enable Partner Connect in Setup. See Set Up Partner Connect as a Partner in Salesforce Help.

Fields 

EventOrderInBatch 

Type: int

Properties: Create, Nillable

Description: Order number of the external record share event in the export batch.

EventType 

Type: picklist

Properties: Create, Restricted picklist

Description: Event type of the external record sharing event. Possible values are:

  • RecordDataExport

EventUuid 

Type: string

Properties: Nillable

Description: A universally unique identifier (UUID) that identifies a platform event message.

ObjectData 

Type: textarea

Properties: Create, Nillable

Description: Fields and field values of records included in this export.

ObjectType 

Type: picklist

Properties: Create, Nillable, Restricted picklist

Description: Object type of the exported records. Possible values are: Values are ExtlRecShrLead, ExtlRecShrOpportunity, Lead, or Opportunity.

PublishBatch 

Type: string

Properties: Create, Nillable

Description: ID of the batch being published.

PublishBatchSize 

Type: int

Properties: Create, Nillable

Description: Number of records for all events in the batch being published.

PublishingSystem 

Type: string

Properties: Create, Nillable

Description: ID of the system exporting the records. If the system is a Salesforce org, this value is the org ID. The vendor system is always a Salesforce org.

ReplayId 

Type: string

Properties: Nillable

Description: Represents an ID value that is populated by the system and refers to the position of the event in the event stream. Replay ID values aren’t guaranteed to be contiguous for consecutive events. A subscriber can store a replay ID value and use it on resubscription to retrieve missed events that are within the retention window.