Newer Version Available
Platform Event Fields
To define a platform event in Salesforce Classic or Lightning Experience:
- From Setup, enter Platform Events in the Quick Find box, then select Platform Events.
- On the Platform Events page, click New Platform Event.
- Complete the standard fields, and optionally add a description.
- For Event Type, select High Volume.
- Click Save.
- To add a field, in the Custom Fields & Relationships related list, click New.
- Follow the custom field wizard to set up the field properties.
Standard Fields
Platform events include standard fields. These fields appear on the New Platform Event page.
| Field | Description |
|---|---|
| Label | Name used to refer to your platform event in a user interface page. |
| Plural Label | Plural name of the platform event. |
| Starts with a vowel sound | If it’s appropriate for your org’s default language, indicate whether the label is preceded by “an” instead of “a.” |
| Object Name | Unique name used to refer to the platform event when using the API. In managed packages, this name prevents naming conflicts with package installations. Use only alphanumeric characters and underscores. The name must begin with a letter and have no spaces. It cannot end with an underscore nor have two consecutive underscores. |
| Description | Optional description of the object. A meaningful description helps you remember the differences between your events when you are viewing them in a list. |
| Deployment Status | Indicates whether the platform event is visible to other users. |
Custom Fields
- Checkbox
- Date
- Date/Time
- Number
- Text
- Text Area (Long)
The maximum number of fields that you can add to a platform event is the same as for a custom object. See Salesforce Features and Edition Allocations.
ReplayId System Field
Each event message is assigned an opaque ID contained in the ReplayId field. The ReplayId field value, which is populated by the system when the event is delivered to subscribers, refers to the position of the event in the event stream. Replay ID values are not guaranteed to be contiguous for consecutive events. For example, the event following the event with ID 999 can have an ID of 1,025. A subscriber can store a replay ID value and use it on resubscription to retrieve events that are within the retention window. For example, a subscriber can retrieve missed events after a connection failure. Subscribers must not compute new replay IDs based on a stored replay ID to refer to other events in the stream.
API Name Suffix for Platform Events
When you create a platform event, the system appends the __e suffix to create the API name of the event. For example, if you create an event with the object name Low Ink, the API name is Low_Ink__e. The API name is used whenever you refer to the event programmatically, for example, in Apex.